With the advent of mass market digital communications, applications and content distribution, many access networks such as wireless networks, cable networks and DSL (Digital Subscriber Line) networks are pressed for user capacity, with, for example, EVDO (Evolution-Data Optimized), HSPA (High Speed Packet Access), LTE (Long Term Evolution), WiMax (Worldwide Interoperability for Microwave Access), DOCSIS, DSL, and Wi-Fi (Wireless Fidelity) becoming user capacity constrained. In the wireless case, although network capacity will increase with new higher capacity wireless radio access technologies, such as MIMO (Multiple-Input Multiple-Output), and with more frequency spectrum and cell splitting being deployed in the future, these capacity gains are likely to be less than what is required to meet growing digital networking demand.
Similarly, although wire line access networks, such as cable and DSL, can have higher average capacity per user compared to wireless, wire line user service consumption habits are trending toward very high bandwidth applications and content that can quickly consume the available capacity and degrade overall network service experience. Because some components of service provider costs go up with increasing bandwidth, this trend will also negatively impact service provider profits.
Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings.
The invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention. Unless stated otherwise, a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. As used herein, the term ‘processor’ refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.
A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.
As wireless networks, such as mobile networks, evolve towards higher bandwidth services, which can include or require, for example, various levels of Quality of Service (QoS) (e.g., conversational, interactive data, streaming data, and/or various (end-to-end) real-time services that may benefit from QoS), demands will increase for converged network services to facilitate such services for end-to-end services between networks (e.g., to allow for control and/or support for such services, for example, QoS support, across network boundaries, such as between wireless networks (such as various service provider networks) and IP networks (such as the Internet), and/or other networks). While various efforts have attempted to address such QoS needs, such as policy management frameworks for facilitating QoS end-to end solutions, there exists a need to facilitate various QoS requirements using device assisted services.
Accordingly, Quality of Service (QoS) for Device Assisted Services (DAS) are provided. In some embodiments, QoS for DAS is provided.
To establish a QoS channel, differentiated services are typically available, in which one class/level of service has a higher priority than another to provide for differentiated services on a network, such as a wireless network. For example, in a wireless network, various network elements/functions can be provisioned and controlled to establish a single end or end to end QoS channel. In some embodiments, a centralized QoS policy coordination and decision function using Device Assisted Services (DAS) techniques to assist in coordinating the QoS channel setup and control among the various elements of a wireless network is provided.
In some embodiments, QoS channel refers to the logical communication channel connected to a device that provides a desired level of QoS service level. For example, the QoS channel can be created with one or more QoS links, in which each link represents a QoS enabled connection that spans a portion of the total end to end network communication path from a near end device to a far end device. For example, the far end device can be on the same network or on a different network, potentially with different access technology and/or a different access network carrier. In some embodiments, the QoS channel includes one or more QoS links in which each link in the channel is QoS enabled, or one or more of the links in the channel is QoS enabled and others are not. As an example, a QoS channel can include the following . . . a first device traffic path link, a first device to access network equipment element link (e.g. 2G/3G/4G wireless base station, WiFi access point, cable network head end, DSLAM, fiber aggregation node, satellite aggregation node, or other network access point/node), a first carrier core network, a long haul IPX network, a second carrier core network, a second device to access network equipment element link, and a second device traffic path link as similarly described herein with respect to various embodiments.
In some embodiments, each of the links described above have the ability to provide QoS services for that segment of an overall QoS channel. In some embodiments, the device traffic path link and/or the device to access network equipment element link are QoS enabled, but the carrier core network and/or IPX network links are not QoS enabled. In some embodiments, the core network and/or IPX network have sufficient over-provisioning of bandwidth that QoS is not limited by these network elements and, for example, can be limited by the device traffic link and/or the device to access network equipment element link do not have sufficient excess bandwidth making it desirable to QoS enable these QoS channel links. A common example is a 2G/3G/4G wireless network in which a device traffic path link and the device to access network element link (e.g., Radio Access Bearer (RAB)) are QoS enabled while the carrier core network and IPX network links are not (e.g., are provided at a best effort service level or other service levels).
In some embodiments, a QoS session refers to the QoS enabled traffic for a given device that flows over a QoS channel or QoS link. This QoS traffic supports a QoS service activity. In some embodiments, a QoS service activity includes a device service usage that is requested, configured, or preferably serviced with a given level of QoS. In some embodiments, a device QoS activity is a combination of one or more of the following: application, destination, source, URL or other similar service identifier, service provider, network type, traffic type, content type, network protocol, session type, QoS identifier, time of day, network capacity (e.g., network busy state), user service plan authorization or standing, roaming/home network status, and/or other criteria/measures as similarly described herein. For example, QoS service activities that are supported by QoS sessions can include VOIP traffic, streaming video traffic, differentiated access bandwidth during busy network periods, real-time interactive traffic, such as network connected multimedia meetings (e.g., shared presentations, picture, video, voice, and/or other such applications/services), best effort interactive such as Internet browsing, time sensitive services, such as email message body delivery, near real time interactive services, such as SMS or push to talk, background download services, such as email downloads and other file transfers (e.g., FTP), and/or truly background download services, such as software updates.
In some embodiments, various QoS levels or classes are supported. For example a conversation class can provide for real-time traffic, which is typically very delay sensitive but can tolerate bit errors and packet losses. The conversational class is typically used for Voice Over IP (VOIP) and video telephony, in which users of such services benefit from the short delay features of the conversational class) A streaming class is similar to the conversational class except that the streaming class is typically can tolerate more delay than the conversational class. The streaming class is generally used for one end of the connection is a user (e.g., human user) and the other end is a machine/computer (e.g., for streaming content applications, such as streaming of video, such as movies or other video content). An interactive class is generally intended for traffic that allows delay variation while requiring reasonably low response time (e.g., web browsing or other applications in which the channel can be unused for long periods of time but when a user makes a request for a new page/data, the response time should be reasonably low). A background class is generally used for lowest priority service usages (e.g., typically used for e-mail, software updates, and/or other similar applications). In some embodiments, various QoS classes or services are applicable to the conversational class. In some embodiments, various QoS classes or services are also applicable to the streaming class. In some embodiments, various QoS classes or services are also applicable to the interactive class but typically not applicable to the background class. As will now be apparent to one of ordinary skill in the art, various other classes can be provided with lower or higher granularity based on service usage/channel requirements and/or network architectures.
In some embodiments, a QoS link or a QoS channel supports one QoS session. In some embodiments, a QoS link or a QoS channel supports multiple QoS sessions. In some embodiments, QoS link provisioning is provided to setup the QoS traffic level for a given QoS session or group of QoS sessions.
In some embodiments, a QoS channel is a single ended QoS channel or an end to end QoS channel. For example, if a QoS channel is end to end, then the QoS channel provisioning is accomplished in a coordinated manner for each QoS enabled link in the QoS channel. If a QoS channel is single ended, then the network elements and/or device participate in provisioning as much of one end of the QoS channel as possible, leaving provisioning of the QoS for the other end of the channel as the responsibility of the device and/or network elements that handle the traffic at the other end of the QoS channel. In some embodiments a single ended QoS channel includes another single ended QoS channel at the other end. In some embodiments, only one end has single ended QoS channel enablement while the other end of the channel is a best effort service level, which, for example, can be used where one end of the QoS channel has tighter constraints on traffic capacity or quality than the other end (e.g., a VOIP call with one end that is QoS enabled on a 3G wireless network that has relatively tight bandwidth compared to a lightly loaded cable modem network device on the other end which may not need to be QoS enabled in order to achieve adequate voice quality).
In some embodiments, a QoS request (e.g., a QoS channel request or QoS service request) is a request for a QoS provisioning event to enable a QoS channel for one or more QoS service activities. In some embodiments, QoS availability assessment includes determining whether one or more of the links in a possible QoS channel are available (e.g., based on network capacity and transmission quality) to provision the necessary level of QoS for a requested QoS channel. In some embodiments, a QoS request is initiated by a device, a user, an application, and/or a network element/function as similarly described herein.
In some embodiments, a service plan refers to the collection of access service capabilities and/or QoS capabilities that are associated with a communications device. In some embodiments, the access and/or QoS capabilities are determined by the collection of access service control policies for the device. In some embodiments, these service control policies are implemented in the network equipment. In some embodiments, these access service control policies are implemented both in the device and in the network equipment. In some embodiments, these access service control policies are implemented in the device. In some embodiments, there are different levels of service control capabilities (policies) based on different levels of service plan payments or device standing or user standing. In some embodiments, there are different levels of service control policies based on network type, time of day, network busy status, and/or other criteria/measures as similarly described herein with respect to various embodiments. In some embodiments, the access control and QoS control policies are based on the type of service activity being sought. In some embodiments, the QoS level and access level available for a given service activity for a given device or user is determined by the policies associated with the service plan. In some embodiments, a QoS authorization assessment is performed to determine whether a device or user has sufficient service plan standing to allow the requested level of QoS.
In some embodiments, before a QoS channel or link is provisioned (or before a QoS request is responded to or filled), a QoS availability assessment is performed to determine whether sufficient communication channel resources are available to provision the necessary level of QoS for the QoS channel or link. In some embodiments, this QoS availability assessment is determined by assessing the available QoS capacity for one or more necessary QoS links in the channel. For example, the available QoS link capacity can be assessed for one or more of a device traffic path, a device to access network equipment element link, a core network link, and/or an IPX network link. If the QoS assessment shows that the necessary channel capacity and quality is available for the desired QoS level for one or more desired QoS service activities, then a QoS channel request or QoS service request can be granted. In some embodiments, a QoS link or QoS channel reservation process is provided to reserve QoS capacity and quality in advance of link or channel provisioning to ensure that the available QoS resources are not assigned between the time of QoS availability assessment and QoS channel provisioning.
In some embodiments, the QoS availability assessment is performed after QoS authorization assessment. This prevents the unnecessary exercising of network elements when the device or user does not have sufficient service plan standing to receive the desired level of QoS even if it is available. This can be an important screening function performed on the device in the service processor, or by a centralized network function such as the service controller (or interchangeably the home agent, HLR, AAA, base station, one of the gateways or other network element/function). In some embodiments, QoS availability is assessed without conducting a QoS authorization assessment or before receiving the response to a QoS authorization assessment.
In some embodiments, a QoS channel is provisioned to create the QoS channel to support a QoS session (e.g., a QoS service activity). In some embodiments, QoS channel provision includes assigning, routing, and/or otherwise causing the QoS session traffic to flow over one or more QoS links in the assigned QoS channel.
In some embodiments, device assisted service traffic control and QoS apply readily and directly to the problems of managing a QoS device link for QoS channel provisioning. Accordingly, in some embodiments, a service provider is provided to assist in provisioning the device portion of the QoS channel. In some embodiments, the service processor provisions the device link portion of the QoS channel by placing a higher priority on higher QoS level traffic. In some embodiments, this QoS priority is implemented in a number of ways, including routing the higher priority QoS traffic into first priority in the downstream and/or upstream traffic queues. Upstream traffic queuing is performed directly in some embodiments by transmitting guaranteed bit rate traffic first at higher available throttling rates, differentiated QoS traffic second with a controlled throttling rate, best effort traffic third with possibly lower controlled throttled rates, and/or background traffic fourth when/if bandwidth not needed by the higher levels of QoS traffic and at lower controlled throttling rates. For example, downstream traffic can be handled by queuing traffic and delaying or preventing TCP acknowledgements to be returned for the lower levels of QoS priority, while immediately passing the traffic and TCP acknowledgements for higher levels of QoS priority. The device link portion of the QoS channel is thus provisioned by assigning policies for the queuing priority, delay, throttle rate and TCP acknowledgement return rate for device traffic in accordance with the bandwidth that is available at any point in time for the device. In some embodiments, various device service processor traffic control capabilities regulate or partially regulate QoS in accordance with a set of network policy instructions, including, in some embodiments, a service plan policy set.
In some embodiments the device service processor establishes multiple QoS channels through the device traffic path with each QoS channel having traffic control policies as described herein, with each QoS channel policy set creating a different class of QoS. In some embodiments, employing this multiple QoS channel approach, QoS for a given service activity is provided by routing the traffic for that QoS activity to the appropriate QoS channel with the appropriate QoS policy settings. The routing to the appropriate QoS channel can be provided using various techniques. For example, the routing can be provided by applying a common service traffic control policy set to traffic associated with all QoS service activities that require or request the QoS provided by the common service traffic control policy set. The application of the service traffic control policy set can be accomplished in a number of ways utilizing the embodiments described for the policy implementation agent and the policy control agent described herein. In such embodiments, the problem of assigning a QoS channel to a number of QoS service activities is reduced to applying a pre-determined set of service traffic control policies to each of the QoS service activities, with each pre-determined set of service traffic control policies representing a different QoS class. The device can then manage the overall QoS for all traffic based on the available traffic capacity and quality, the total aggregate traffic demand for each QoS traffic class and the policy rules that determine how each traffic class is provided with differential bit rate and traffic quality as compared to the other traffic classes for a given level of available traffic capacity and quality.
Based on the aggregate demand for each traffic QoS class, and the traffic capacity and quality level available to the device, the service processor can adjust the total available bit rate or percentage of available traffic capacity for each QoS class. For example, in some embodiments, the aggregate demand for the real time interactive traffic control class (e.g. services, such as VOIP, emergency communication services or high performance real time competitive gaming) can be determined, and the QoS routing function on the device (e.g., a QoS router agent/function) can first allocate enough constant bit rate traffic capacity from the available traffic capacity to satisfy these services, with each QoS service activity that requires this QoS class being assigned to this QoS channel. As more QoS service activities require this traffic class, the capacity allocated to the QoS channel out of the available device capacity is increased, and when fewer QoS service activities require this traffic class the capacity for this QoS channel is released. In the event that the device does not have any more available capacity with a guaranteed bit rate QoS level, then additional QoS service activities that desire, require or request this QoS level will not be provided this QoS level, and instead will either be provided with a lower QoS level or will not be allowed to connect to the access network. In some embodiments, there can be a hierarchy among the possible QoS service activities so that if there is no more capacity available at a given service QoS level, then the available capacity for that QoS class is provided to the service activities requiring that QoS from highest priority to lowest, until the available QoS class capacity is consumed, and then one or more QoS service activities that are too low on the priority list to obtain service with that QoS class are either bumped to a lower QoS class or are denied access. In some embodiments, once the required capacity to satisfy the real time constant rate traffic needs is satisfied, the remaining capacity available to the device is then divided among the other QoS channel classes in accordance with a priority policy, with the priority policy being based on the relative priority of each service class, the relative priority of each QoS service activity, or a combination of the relative priority of each QoS service class and each QoS service activity. For example, these relative priority policies can vary from device to device based on service plan selection, device type, user standing, user group, device location, device network connection, type of network, time of day, network busy state, and/or other criteria/measure.
In some embodiments, a QoS link is established between the device and an access network equipment element. For example, such equipment element embodiments can include a 2G/3G/4G wireless base station, a wireless access point, a cable network head end, a DSL network DSLAM, a fiber network device traffic aggregator, a satellite network device traffic aggregator, a frame relay aggregation node, an ATM aggregation node, and/or other network equipment. In some embodiments, a logical communication channel is created between the device and the network equipment element, with the logical communication channel supporting a given level of QoS or QoS class traffic policy set. For example, the logical channel can include a RAB formed between a 2G/3G/4G base station and a wireless end point device. The RAB can be formed by controlling the media access control (MAC) parameters of the base station radio channel so that a given level of QoS class policies can be implemented. For example, the RAB can support constant bit rate, low latency communication traffic for guaranteed bit rate real time traffic, or a differentiated high priority access channel for streaming traffic, or a best effort random access channel for best effort traffic, or an available unused capacity traffic for background traffic. The QoS channel link created in this manner can be dedicated to a single device, or shared with a subset of devices, or available to all devices. The QoS channel link created in this manner can be used by the device to support a single QoS activity as described herein, or a group of QoS activities as described herein. It will now be apparent to one of ordinary skill in the art that similar settings for cable head end and cable modem MAC can yield similar QoS classes for QoS links for the cable modem case and that similar techniques can be applied for a wireless access point or a satellite system MAC to achieve similar QoS classes for QoS links. It will also now be apparent to one of ordinary skill in the art that by creating multiple logical channels in the device link, and/or adjusting the available access network capacity and quality for each logical device communication channel in the DSLAM or fiber aggregator, similar QoS class QoS links can be established for the DSL and fiber distribution network cases.
In some embodiments the device service processor serves to route QoS service activities to the appropriate logical communication channel established for the desired QoS class supported by a QoS link between the device and the access network equipment element. In some embodiments, the device service processor elements (e.g., the policy implementation agent and/or the policy control agent) can be used in some embodiments to assign the same QoS traffic control policies to one or more QoS service activities that require the same QoS level. In a similar manner, in some embodiments, the device service processor elements can be used to assign or route service activity traffic for a given QoS class to the correct logical communication channel between the device and the access network element (e.g., a 2G/3G/4G base station) that supports the traffic control policies for the desired QoS class. For example, a QoS service link that supports guaranteed bit rate and latency can be established with one or more RABs from a base station to the device, and a second QoS service link can be established that supports differentiated preferred access for streaming content using one or more differentiated access RABs, and a third best effort RAB can be used to support best effort traffic. Each of the required RABs is first requested and then provisioned as described herein based on the aggregate required capacity and quality for one or more QoS service activities that require or desire the specific QoS service class associated with the RAB logical channel policy parameters. Once the set of logical QoS channels is thus established, the service processor (e.g., QoS router agent/function) routes the traffic associated with each QoS service activity to the appropriate RAB. In some embodiments, the service processor can detect increases or decreases in aggregate QoS class demand for each QoS class as QoS activities are initiated or terminated for that QoS class, and the service processor can communicate the required increases or decreases in the RAB assignments required to support that logical QoS channel.
In some embodiments, the access QoS link is established by direct communication from the device in which the device requests the QoS channel or link from the access network equipment element, or the device requests the QoS channel or link from an intermediate networking device, such as a service controller (e.g., or a readily substituted device with similar features, such as a home agent, an HLR, a mobile switching center, a base station, an access gateway, a AAA system, or a billing system). In some embodiments, the device service processor bases the QoS channel or link request on an association the device performs to match a QoS service activity with a desired or required QoS class or QoS traffic control policy set. For example, this association of QoS class or QoS traffic control policy set with QoS service activity can be determined by a predefined policy mapping that is stored on the device and used by the service processor. In some embodiments, this policy mapping store is populated and/or updated by a service controller (e.g., or similar function as described herein). In some embodiments, the mapping is determined by a service controller (e.g., or similar function as described herein) based on a report from the device of the QoS service activity that needs the QoS channel or link.
In some embodiments, the required or desired QoS level for one or more QoS service activities is determined by a set of QoS service traffic control policies that are pre-assigned to various QoS service activities. For example, a given application can be pre-assigned a QoS class. As another example, a web service destination such as a VOIP service site can be assigned a QoS class. As another example, a given application can have one QoS assignment level for general Internet traffic but have a QoS assignment for real-time gaming traffic. As another example, a real-time broadcasting website can have a best effort QoS level assigned to programming information and general browsing and have a differentiated streaming QoS level for broadcast traffic content. In some embodiments, detection of QoS need or QoS assignment request for a given activity can be assigned by a device service processor according to a pre-defined QoS policy rules table (e.g., QoS activity table), or can be determined by a service controller based on information reported by the device, or can be requested by an application through a QoS application interface (e.g., QoS API), or can be determined by the nature of incoming traffic.
In embodiments, in which both end points in the QoS channel participate in establishing an end to end QoS channel, the required QoS level is determined and/or communicated by the originating end point. In some embodiments, the required QoS level is determined and/or communicated by the receiving end point. In some embodiments the QoS level is determined and/or communicated by the originating end point service controller (e.g., or the access network element (such as a base station), the HLR, home agent, mobile switching center, AAA, gateway, or other network element/function). In some embodiments, the QoS level is determined and/or communicated by the receiving end point service controller (e.g., or alternatively the access network element (such as a base station), the HLR, home agent, mobile switching center, AAA, gateway, or other network element/function). In some embodiments, the receiving end point service controller (e.g., or the access network element (such as a base station), the HLR, home agent, mobile switching center, AAA, gateway or other network function) and the originating end point service controller (e.g., or other similar function) communicate with one another to coordinate establishment of the QoS channel between the end points.
In some embodiments, the near end or originating end device service processor contacts the far end or terminating device service processor to initiate a QoS channel. In some embodiments, the initiation of the QoS channel from the near end or originating device is performed automatically by the far end device when its service processor detects that a given level of QoS is needed for the communication between the two devices. In some embodiments, the near end or originating device service processor detects the need for a QoS channel to the far end or terminating device and contacts a central network resources, such as the service controller (e.g., or other equipment element with similar function for this purpose), and the service controller provisions the far end of the QoS channel, either by communicating directly with the far end device or by communicating with the far end device's service controller (e.g., or other equipment element with similar function for this purpose). In some embodiments, in which the far end device service controller is contacted to assist in provisioning the QoS channel, there is a look up function to determine the address of the far end service controller based on a look up index formed from some aspect of the far end device credentials (e.g., phone number, SIM I.D., MEID, IMSI, IP address, user name, and/or other device credentials).
In some embodiments, the mapping of QoS service activity to the desired level of QoS class or QoS traffic control policies is determined by providing a QoS API in the device service processor that applications use to request a QoS class or QoS channel connection. In some embodiments, an API is provided so that application developers can create application software that uses the standard interface commands to request and set up QoS channels. In some embodiments, the API does one or more of the following: accepts QoS requests from an application, formats the QoS channel request into a protocol appropriate for transmission to network equipment responsible for assessing QoS channel availability (e.g., including possibly the device traffic control system), coordinates with other network elements (e.g., including possibly the device traffic control system) to reserve a QoS channel, coordinates with other network elements (e.g., including possibly the device traffic control system) to provision a QoS channel, informs the application that the desired QoS channel can be created or not, and/or coordinates with other network elements (e.g., including possibly the device traffic control system) to connect the application with the desired QoS channel class. In some embodiments, the QoS API accepts the application QoS request and communicates and possibly coordinates with one or more QoS network equipment elements, such as a base station, cable head end or access point. In some embodiments, the QoS API accepts the QoS request from the application and communicate and possibly coordinates with an intermediate network element, such as a service processor (e.g., or other similar function as described herein). In some embodiments the QoS API assesses the QoS service plan standing for the device or user before sending QoS channel requests to other network elements, and only initiates the QoS request sequence if required service plan authorization is in place. In this manner, the potentially complex process of establishing a QoS channel with all the specific equipment communication protocols that typically need to be supported to assess QoS channel availability and provision the QoS channel are simplified into a limited set of API commands that are easy for an application development community to learn about and use for QoS differentiated services and applications.
In some embodiments, local traffic control on the device service processor is combined with traffic control in the link between the device and the access network equipment element. In this manner, both the device traffic control path QoS link and the device to access network element QoS link can be coordinated for best device QoS performance results given the available capacity and quality of the access network traffic for the device. In some embodiments the policies for how the device manages local traffic control, establishes access network element logical channels (e.g., RABs) and routes traffic to and from the access network element logical channels is all determined by pre-defined policy rules loaded onto the device by the service controller (or other equivalent network element). In some embodiments, these policies are determined in the service controller itself.
In some embodiments, a QoS user interface (e.g., QoS UI) is presented to the device user. In some embodiments, the QoS UI notifies the user what level of QoS services the device is authorized to receive based on the service plan selection. In some embodiments, the QoS UI notifies the user what level of QoS services are available on the present network the device is connected to at the present time. In some embodiments, the QoS UI notifies the user when a level of QoS service that is higher than that authorized by the user service plan is required or desirable for a given service activity that the device has initiated. In some embodiments, the QoS UI provides the user with a set of one or more upgrade options to upgrade the service plan to include a higher level of QoS for one or more service activities. In some embodiments, the QoS UI provides the user with an opportunity to specify what level of QoS the user would like to employ for one or more service usage activities. In some embodiments, the QoS UI allows the user to specify a service plan setting that provides differentiated QoS during times when the network is busy. In some embodiments, the QoS UI allows the user to purchase one or more grades of service QoS with either a post-pay for a pre-defined service period and one or more pre-defined service usage limits by QoS class, a pre-pay for one or more pre-defined service usage limits by QoS class, or another payment system for differentiated QoS services. In some embodiments the QoS UI provides the user with an opportunity to QoS enable or pay for QoS services for a connection that is initiated by an incoming connection to the device.
In some embodiments, QoS for DAS techniques include verifying that the device is properly implementing the QoS traffic control policies, for example, in accordance with a service plan. This ensures that errors, hacking, user device software settings manipulations, or other malware events do not result in inappropriate levels of QoS for a given device or group of devices. Accordingly, in some embodiments, the traffic control and QoS verification techniques described herein are employed to verify that the proper level of QoS is applied for a given service usage activity in accordance with a QoS priority policy. For example, verification of QoS channel request policy rules behavior can be implemented in a variety of ways including, as an example, monitoring device QoS channel requests and comparing the level of QoS requested with the level of QoS the device is authorized to receive in the service plan in effect for the device. Verification of proper QoS channel usage behavior by a device can be implemented in a variety of ways including, for example, monitoring network based reports of QoS service usage and comparing the network based reports against the service policy rules that should be in effect given the device service plan. Verification of proper device traffic control to implement a QoS service policy that is in effect can be accomplished in a variety of ways by verifying that the appropriate traffic control policy rules are being properly implemented as described herein.
In some embodiments, the QoS router prioritizes traffic on the device. In some embodiments, the QoS router connects the QoS enabled session to the RAB that has the proper QoS level. In some embodiments, one session is routed to the RAB. In some embodiments, more than one session can be routed to an RAB. In some embodiments, multiple RABs providing multiple QoS levels are created to the device, and the QoS router routes each service activity to the RAB dictated by the QoS policy rules in effect on the device.
In some embodiments, the network collects service usage charges for different QoS classes. In some embodiments, there is differentiated service charging for the different classes of QoS service usage. As an example, since guaranteed bit rate traffic consumes network resources whether the traffic capacity is used or not, there can be a time element involved in the charging calculations. As a more detailed example, guaranteed bit rate services can be charged by the total bandwidth provisioned to the device at a given time multiplied by the amount of time that that bandwidth is made available. In some embodiments, differentiated access traffic that has higher QoS than best effort traffic but is not guaranteed bit rate can be charged at a higher rate than best effort traffic but lower than guaranteed bit rate. Such traffic in some embodiments can be charged based on the time the QoS channel is made available and the total amount of data transmitted over the channel, or can only be based on the total amount of data transmitted over the channel. Best effort traffic is charged in some embodiments based only on the total amount of data used, with the data charges being less than differentiated streaming access services. Background data services in some embodiments are charged at the lowest rate, possibly with only certain times of the day or periods of low network traffic demand being available for such services, and with the service being based on total data transmitted. In some embodiments, all QoS service levels can be charged based on a fixed price for a fixed charging period, possibly with a service usage cap with additional charges if the service cap is exceeded. In such fixed price scenario embodiments, the price charged is again higher for higher levels of QoS.
In some embodiments, the network equipment (e.g., access network element, gateways, AAA, service usage storage systems, home agent, HLR, mobile data center, and/or billing systems) record and report service usage for one or more of the QoS service classes used by the device. In some embodiments, the device service processor records and reports service usage for one or more of the QoS service classes used by the device and reports the QoS service class usage to the service controller (e.g., or other substitute network element). In some embodiments, in which the device is recording reporting usage for one or more QoS service classes, it is important to verify the device service usage reports to ensure that the device usage reports are not distorted, tampered with, and/or otherwise in error. In some embodiments, verifying service usage reports against service usage that should be occurring given the service control policies in place on the device, service processor agent functional operation verification, test service usage events, agent query response sequences, device service processor software protection techniques, device service processor software environment checks, and several other techniques are provides as described herein. For example, using one or more of these verification techniques can provide a verifiable device assisted QoS service usage charging system.
In some embodiments, device assisted traffic control is provided for managing network congestion as follows. When a given base station or group of base stations experience traffic demand that is high relative to the available capacity and/or service quality that can be provided, and such a condition is detected by means of network busy state assessment as described below, then a service controller (e.g., or other interchangeable network function) can issue traffic control throttling policies to the devices in accordance with a measure of the excess traffic demand the one or more base stations is experiencing. For example, the device service processors connected to an overly busy base station can be instructed to reduce the traffic control priority for one or more classes of QoS traffic, reducing the queuing priority, throttling rate, delay and/or access allowance for some or all of one or more classes of traffic. As another example, background download processes, such as software updates can be turned off completely or throttled back significantly. As another example, best effort traffic such as Internet browsing can be throttled or reduced for a group of devices connected to base stations experiencing excess traffic demand. As another example, a policy can be implemented on the devices connected to busy base stations in which the device is allowed to browse or conduct other best effort service activities at a relatively high throttling rate for a period of time, but if the device uses more than a certain amount of service (e.g., total data downloaded and/or uploaded) in a certain period of time then the device may be traffic controlled according to an adaptive throttling policy as described in previous disclosures. In some embodiments, higher QoS level traffic cannot be throttled in such circumstances, such as VOIP traffic where real time guaranteed bit rate is important to meet user service needs or expectations, while lower priority traffic such as interactive browsing and/or background download are throttled and/or blocked. In some embodiments, the QoS availability assessment processes described herein are adjusted so that higher QoS channels are not provided and provisioned in times or locations in which a given base station or group of base stations experience excess demand or demand above a given threshold.
In some embodiments, users or devices that have service plans with higher QoS levels, or service plans with higher priority during busy network periods have different traffic control policies applied to them that result in a higher level of traffic performance and/or a higher level of QoS service availability. For example, emergency service workers can be given higher traffic control access policies that result in differentiated services during peak busy times on the network or a portion of the network. In some embodiments, users can obtain a premium service plan for differentiated access during peak busy time periods or may use higher levels of QoS service settings and/or service plans to achieve differentiated service during peak busy periods. As another example, services that demand high QoS, such as real time voice services, instant messaging, push to talk, differentiated video streaming, and/or interactive gaming, are not traffic controlled to the same extent that other lower priority services or lower class service plans are traffic controlled during peak busy times. For example, this type of service differentiation can also be applied based on device type, user group, user standing, user reward zone points, other criteria/measures as similarly described herein.
In some embodiments, the decision to reduce the access traffic control settings as described above is made by the device service processor based on the device's assessment of the network capacity, which can determined using various techniques as described herein. In some embodiments, the decision to reduce the access traffic control settings as described above is made by a service controller (e.g., or other interchangeable network equipment element or elements as described herein) connected to the device that provides instructions to the device to adjust the access policy settings. For example, the service controller can obtain the network capacity information from access equipment elements, from device reports of traffic capacity and/or quality as described herein, or from reports on traffic capacity and/or quality obtained from dedicated devices used for the purpose of assessing network capacity. In some embodiments, the decision to reduce the access traffic control settings as described above is based on the time of day or day of week or both to accommodate cyclical patterns in network capacity and traffic demand.
In some embodiments, a service controller (e.g., or other interchangeable network equipment element or elements as described elsewhere) assesses network busy state and then controls device traffic demand by reducing the offered capacity for one or more service classes supported by the access network equipment elements such as a wireless base station. In such embodiments, the service controller (e.g., or similar function) gathers the network capacity information with one of the techniques described herein and instructs one or more of the access network equipment elements to reduce the offered capacity for one or more levels of service QoS, to one or more of the devices connected to the access network equipment elements. For example, the determination of which devices to throttle back can be made based on an equal throttling of all devices of a given service plan status, or based on the device traffic usage patterns in the recent past as described herein, or based on a combination of service plan status and recent traffic usage patterns.
In some embodiments, the device is enabled with ambient services that have differentiated QoS services as part of the ambient service offering. For example, this can be accomplished using the pre-assigned QoS policies for a given service activity set within the ambient service, or using an ambient service application that requests QoS through the QoS API. Other embodiments for providing QoS differentiated service activities within ambient service offerings will now be apparent to one of ordinary skill in the art.
In some embodiments, the QoS service control policy is adapted as a function of the type of network the device is connected to. For example, the QoS traffic control policies and/or the QoS service charging policies can be different when the device is connected to a wireless network (e.g., a 3G/4G network where there is in general less available QoS enabled traffic capacity) than when the device is connected to a wired network (e.g., a cable or DSL network where there is in general a higher level of QoS capacity available). In such embodiments, the device service processor and the service controller can coordinate to adapt the QoS service control policies and/or the QoS service charging policies to be different depending on which network the device is connected to. Similarly, the device QoS service control policy and/or QoS service charging policy can also be adapted based on whether the device is connected to a home wireless network or a roaming wireless network.
In some embodiments, various of the QoS related techniques described herein are performed on the device using DAS techniques and/or on the service controller in secure communication with a verified service processor executed on the device using DAS techniques. In some embodiments, various of the QoS related techniques described herein are performed by/in coordination/communication with one or more intermediate network elements/functions for assisting in various QoS functions.
As shown,
In some embodiments, service usage information includes network based service usage information (e.g., network based service usage measures or CDRs, which can, for example, be generated by service usage measurement apparatus in the network equipment), which is obtained from one or more network elements (e.g., BTS/BSCs 125, RAN Gateways (not shown), Transport Gateways (not shown), Mobile Wireless Center/HLRs 132, AAA 121, Service Usage History/CDR Aggregation, Mediation, Feed 118, or other network equipment). In some embodiments, service usage information includes micro-CDRs. In some embodiments, micro-CDRs are used for CDR mediation or reconciliation that provides for service usage accounting on any device activity that is desired. In some embodiments, each device activity that is desired to be associated with a billing event is assigned a micro-CDR transaction code, and the service processor 115 is programmed to account for that activity associated with that transaction code. In some embodiments, the service processor 115 periodically reports (e.g., during each heartbeat or based on any other periodic, push, and/or pull communication technique(s)) micro-CDR usage measures to, for example, the service controller 122 or some other network element. In some embodiments, the service controller 122 reformats the heartbeat micro-CDR usage information into a valid CDR format (e.g., a CDR format that is used and can be processed by an SGSN or GGSN or other network elements/equipment used/authorized for generating or processing CDRs) and then transmits it to a network element/function for CDR mediation (e.g., CDR Storage, Aggregation, Mediation, Feed 118).
In some embodiments, CDR mediation is used to account for the micro-CDR service usage information by depositing it into an appropriate service usage account and deducting it from the user device bulk service usage account. For example, this technique provides for a flexible service usage billing solution that uses pre-existing solutions, infrastructures, and/or techniques for CDR mediation and billing. For example, the billing system (e.g., billing system 123 or billing interface 127) processes the mediated CDR feed from CDR mediation, applies the appropriate account billing codes to the aggregated micro-CDR information that was generated by the device, and then generates billing events in a manner that does not require changes to the existing billing systems (e.g., using new transaction codes to label the new device assisted billing capabilities). In some embodiments, network provisioning system 160 provisions various network elements/functions for authorization in the network, such as to authorize certain network elements/functions (e.g., CDR storage, aggregation, mediation, feed 118 or other network elements/functions) for providing micro-CDRs, reformatted micro-CDRs, and/or aggregated or reconciled CDRs.
As shown in
In some embodiments, various techniques for partitioning of device groups are used for partitioning the mobile devices 100 (e.g., allocating a subset of mobile devices 100 for a distributor, an OEM, a MVNO, and/or another partner or entity). As shown in
Those of ordinary skill in the art will appreciate that various other network architectures can be used for providing device group partitions and a settlement platform, and
In some embodiments, CDR storage, aggregation, mediation, feed 118 (e.g., service usage 118, including a billing aggregation data store and rules engine) is a functional descriptor for, in some embodiments, a device/network level service usage information collection, aggregation, mediation, and reporting function located in one or more of the networking equipment apparatus/systems attached to one or more of the sub-networks shown in
In some embodiments, a service processor download 170 is provided, which provides for periodical downloads/updates of service processors (e.g., service processor 115). In some embodiments, verification techniques include periodically updating, replacing, and/or updating an obfuscated version of the service processor, or performing any of these techniques in response to an indication of a potential compromise or tampering of any service processor functionality and/or QoS functionality executed on or implemented on the device 100.
In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) provides a device/network level service usage information collection, aggregation, mediation, and reporting function. In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) collects device generated/assisted service usage information (e.g., micro-CDRs) for one or more devices on the wireless network (e.g., devices 100); and provides the device generated service usage information in a syntax and a communication protocol that can be used by the wireless network to augment or replace network generated usage information for the one or more devices on the wireless network. In some embodiments, the syntax is a charging data record (CDR), and the communication protocol is selected from one or more of the following: 3GPP, 3GPP2, or other communication protocols. In some embodiments, as described herein, the CDR storage, aggregation, mediation, feed 118 collects/receives micro-CDRs for one or more devices on the wireless network (e.g., devices 100). In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) includes a service usage data store (e.g., a billing aggregator) and a rules engine for aggregating the collected device generated service usage information. In some embodiments, the network device is a CDR feed aggregator, and the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) also aggregates (network based) CDRs and/or micro-CDRs for the one or more devices on the wireless network; applies a set of rules to the aggregated CDRs and/or micro-CDRs using a rules engine (e.g., bill by account, transactional billing, revenue sharing model, and/or any other billing or other rules for service usage information collection, aggregation, mediation, and reporting), and communicates a new set of CDRs for the one or more devices on the wireless network to a billing interface or a billing system (e.g., providing a CDR with a billing offset by account/service). In some embodiments, a revenue sharing platform is provided using various techniques described herein.
In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) communicates a new set of CDRs (e.g., aggregated and mediated CDRs and/or micro-CDRs that are then translated into standard CDRs for a given wireless network) for the one or more devices on the wireless network to a billing interface (e.g., central billing interface 127) or a billing system (e.g., central billing system 123). In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) communicates with a service controller (e.g., service controller 122) to collect the device generated service usage information (e.g., micro-CDRs) for the one or more devices on the wireless network. In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) communicates with a service controller, in which the service controller is in communication with a billing interface or a billing system. In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) communicates the device generated service usage information to a billing interface or a billing system. In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) communicates with a transport gateway and/or a Radio Access Network (RAN) gateway to collect the network generated/based service usage information for the one or more devices on the wireless network. In some embodiments, the service controller 122 communicates the device assisted service usage information (e.g., micro-CDRs) to the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements).
In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) performs rules for performing a bill by account aggregation and mediation function. In some embodiments, the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) performs rules for performing a service billing function, as described herein, and/or for performing a service/transactional revenue sharing function, as described herein. In some embodiments, the service controller 122 in communication with the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) performs a rules engine for aggregating and mediating the device assisted service usage information (e.g., micro-CDRs). In some embodiments, a rules engine device in communication with the CDR storage, aggregation, mediation, feed 118 (and/or other network elements or combinations of network elements) performs a rules engine for aggregating and mediating the device assisted service usage information.
In some embodiments, the rules engine is included in (e.g., integrated with/part of) the CDR storage, aggregation, mediation, feed 118. In some embodiments, the rules engine and associated functions, as described herein, is a separate function/device. In some embodiments, the service controller 122 performs some or all of these rules engine based functions, as described herein, and communicates with the central billing interface 127. In some embodiments, the service controller 122 performs some or all of these rules engine based functions, as described herein, and communicates with the central billing system 123.
In some embodiments, a settlement platform service is provided. For example, micro-CDRs can be aggregated and mediated to associate service usage for one or more services used by a communications device (e.g., a user of the communications device). A rules engine or another function can determine a revenue share allocation for the service usage for a particular service to determine the settlement for such service usage for the revenue sharing allocation/model and to distribute accounting and settlement information to one or more of carriers, distribution partners, MVNOs, wholesale partners, and/or other partners or entities. In some embodiments, the service is a transactional service.
In some embodiments, duplicate CDRs are sent from the network equipment to the billing system 123 that is used for generating service billing. In some embodiments, duplicate CDRs are filtered to send only those CDRs/records for devices controlled by the service controller and/or service processor (e.g., managed devices). For example, this approach can provide for the same level of reporting, lower level of reporting, and/or higher level of reporting as compared to the reporting required by the central billing system 123.
In some embodiments, a bill-by-account billing offset is provided. For example, bill-by-account billing offset information can be informed to the central billing system 123 by providing a CDR aggregator feed that aggregates the device assisted service usage data feed to provide a new set of CDRs for the managed devices to the central billing interface 127 and/or the central billing system 123. In some embodiments, transaction billing is provided using similar techniques. For example, transaction billing log information can be provided to the central billing interface 127 and/or the central billing system 123.
In some embodiments, the rules engine (e.g., performed by the service usage 118 or another network element, as described herein) provides a bill-by-account billing offset. For example, device assisted service usage information (e.g., micro-CDRs) includes a transaction type field or transaction code (e.g., indicating a type of service for the associated service usage information). For example, the rules engine can apply a rule or a set of rules based on the identified service associated with the device generated service usage information to determine a bill-by-account billing offset (e.g., a new CDR can be generated to provide the determined bill-by-account billing offset). In some examples, the determined bill-by-account billing offset can be provided as a credit to the user's service usage account (e.g., a new CDR can be generated with a negative offset for the user's service usage account, such as for network chatter service usage, or transactional service usage, or for any other purposes based on one or more rules performed by the rules engine).
As another example, for a transactional service, a first new CDR can be generated with a negative offset for the user's service usage account for that transactional service related usage, and a second new CDR can be generated with a positive service usage value to charge that same service usage to the transactional service provider (e.g., Amazon, eBay, or another transactional service provider). In some embodiments, the service controller 122 generates these two new CDRs, and the service usage 118 stores, aggregates, and communicates these two new CDRs to the central billing interface 127. In some embodiments, the service controller 122 generates these two new CDRs, and the service usage 118 stores, aggregates, and communicates these two new CDRs to the central billing interface 127, in which the central billing interface 127 applies rules (e.g., performs the rules engine for determining the bill-by-account billing offset).
In some embodiments, the service controller 122 sends the device generated CDRs to the rules engine (e.g., a service usage data store and rules engine, such as CDR storage, aggregation, mediation, feed 118), and the rules engine applies one or more rules, such as those described herein and/or any other billing/service usage related rules as would be apparent to one of ordinary skill in the art. In some embodiments, the service controller 122 generates CDRs similar to other network elements, and the rules (e.g., bill-by-account) are performed in the central billing interface 127. For example, for the service controller 122 to generate CDRs similar to other network elements, in some embodiments, the service controller 122 is provisioned on the wireless network (e.g., by network provision system 160) and behaves substantially similar to other CDR generators on the network).
In some embodiments, the service controller 122 is provisioned as a new type of networking function that is recognized as a valid, authorized, and secure source for CDRs by the other necessary elements in the network (e.g., CDR storage, aggregation, mediation, feed 118). In some embodiments, if the necessary network apparatus only recognize CDRs from certain types of networking equipment (e.g. a RAN gateway or transport gateway), then the service controller 122 provides authentication credentials to the other networking equipment that indicate that it is one of the approved types of equipment for providing CDRs. In some embodiments, the link between the service controller 122 and the necessary CDR aggregation and mediation equipment is secured, authenticated, encrypted, and/or signed.
In some embodiments, the CDR storage, aggregation, mediation, feed 118 discards the network based service usage information (e.g., network based CDRs) received from one or more network elements. In these embodiments, the service controller 122 provides the device assisted service usage information (e.g., device based CDRs or micro-CDRs) to the CDR storage, aggregation, mediation, feed 118 (e.g., the CDR storage, aggregation, mediation, feed 118 can just provide a store, aggregate, and communication function(s), as it is not required to mediate network based CDRs and device assisted CDRs), and the device based service usage information is provided to the central billing interface 127 or the central billing system 123.
In some embodiments, the device based CDRs (e.g., micro-CDRs) and/or new CDRs generated based on execution of a rules engine as described herein are provided only for devices that are managed and/or based on device group, service plan, or any other criteria, categorization, and/or grouping, such as based on ambient service or ambient service provider or transactional service or transactional service provider.
In some embodiments, QoS for DAS includes a service processor (e.g., any device assisted element/function) that facilitates coordination for and/or provisions wireless access/radio access bearers (e.g., RABs). In some embodiments, the service processor determines whether a request for QoS is authorized (e.g., according to QoS service level, user standing, available local network capacity (as reported by other device(s) and/or network)). In some embodiments, device QoS capacity demand reports provide and/or augment network capacity demand reports.
In some embodiments, QoS for DAS includes a service controller (e.g., any network device based service control element/function) that facilitates coordination for and/or provisions wireless access/radio access bearers (e.g., RABs) on a device (e.g., a communications device, such as a mobile wireless communications device and/or an intermediate networking device), on network, and/or on device plus network. In some embodiments, the service controller provides device QoS capacity demand reports to other network equipment/elements/functions, and then also provisions the RAB channel based on various criteria and determinations.
In some embodiments, QoS for DAS provides for device assisted monitoring, information, and/or functionality to facilitate QoS without and/or to assist network based monitoring, information, and/or functionality (e.g., Deep Packet Inspection (DPI) and/or provides such monitoring, information, and/or functionality that may not be available via network based monitoring, information, and/or functionality (e.g., encrypted activities on the device may not be accessible by DPI or other network based techniques). For example, QoS for DAS can assist in the QoS setup to facilitate the QoS setup and provide such information that may not otherwise be available using network based only techniques. For example, device assisted activity and/or service monitoring techniques can assist in classifying the QoS for the monitored activity and/or service using, for example, a QoS activity map (e.g., as described herein or other similar techniques). For example, using such device assisted techniques eliminates and/or minimizes DPI or other network based techniques that can give rise to privacy concerns/issues, network neutrality concerns/issues, and/or otherwise may not be able to provide similar or equivalent granular service/activity monitoring, as discussed above, and/or also off loads such processing from the network (e.g., network elements/devices/functionality) to the communications devices (e.g., at least for such communications devices that can perform such functions, based on their processing and/or memory capabilities, as would be apparent to one of ordinary skill in the art). In some embodiments, QoS for DAS includes the service provider for providing an initial authorization/clearance for a QoS request (e.g., using various techniques described herein), and the service controller determines if the QoS request should be authorized (e.g., based on various QoS authorization/clearance/approval criteria (such as QoS activity maps and/or QoS request rule) and/or network capacity, as described herein). In some embodiments, QoS for DAS includes the service provider for providing a QoS request including a QoS class to the service controller, and the service controller determines if the QoS request should be authorized, as described herein.
In some embodiments, QoS for DAS includes providing or facilitating reports for base station (BTS) for network capacity (e.g., sector, channel, busy state information or network capacity usage/availability, and/or network capacity expected demand) based on, for example, one or more of the following: monitored application usage on the communications device, monitored user activity on the communications device, location of the communications, other available networks, and/or other monitored or determined activity, service usage measure, and/or metric. In some embodiments, at or after execution of an application that is determined to require network service usage (e.g., may require increased wireless network bandwidth, such as based on a service usage activity map), QoS for DAS sends information to the network (e.g., a network controller or other network device element/function) that capacity demand is forthcoming for the communications device (e.g., potentially initiating a provisioning of a QoS radio access bearer (RAB) or other type of RAB).
In some embodiments, network capacity (e.g., busy state information) is collected from one or more communications devices in communication with a wireless network (e.g., network capacity/usage information measured from each respective communications device's perspective is determined and stored by the service processor on each respective communications device) and reported to the service controller, and the service controller (e.g., or another network element/function) uses this information to determine what resources are available for allocation to various levels of QoS (e.g., to respond to/facilitate various QoS requests) and/or to workload balance across multiple base stations and/or networks (e.g., cellular, Wi-Fi, and/or other wireless networks).
In some embodiments, the service processor executed on the communications device sends a QoS request (e.g., a wireless network bearer channel reservation request or Radio Access Bearer (RAB) request) to the service controller. The service controller verifies the request using various verification techniques as described herein. In some embodiments, the service controller facilitates coordination of various device QoS requests with one or more base stations (BTSs) in communication with the communications device to provide for the requested QoS reservation to facilitate the new QoS session. In some embodiments, the service controller provides a QoS routing function by, for example, providing various QoS routing instructions to a device service processor (e.g., aggregating, prioritizing, queuing, authorizing, allocating reservations/RABs, denying, re-routing (such as to other BTSs and/or other networks) and/or otherwise managing QoS requests), in which the BTS may or may not be QoS aware. For example, QoS priority can be based on activity (e.g., service usage and/or application), service level, user standing, network capacity, time of day, and/or QoS priority can be purchased on a transaction basis, a session basis, a pre-pay basis or a plan basis. As another example, QoS priority can also vary by device type, user within a group, group, application type, content type, or any other criteria or measure and/or any combination thereof. In some embodiments, the service controller also facilitates coordination of various device QoS requests with other network elements/functions for QoS implementation and management to provide for an end to end QoS solution.
In some embodiments, QoS can be symmetric for two mobile devices or asymmetric. In some embodiments, QoS resource availability can be from communications devices, BTS(s), other network functions (e.g., service control, service controller and/or any other network elements/functions) or any combination thereof. In some embodiments, the service controller provides QoS demand information to another network element/function. In some embodiments, the service controller provides the central aggregator and policy decision point (PDP). In some embodiments, the service controller controls (e.g., at least in part) QoS related functions for communications devices, BTS(s), and/or a combination of both.
In some embodiments, charging (e.g., monitoring and/or determining associating charging or billing) for QoS service usage/transactions is determined using various techniques described herein. For example, the service processor can assist in charging for QoS activities. In some embodiments, the service processor uses device assisted Charging Data Records (CDRs) or micro-CDRs to assist in charging for QoS activities (e.g., using QoS class related transaction codes), as described herein with respect to various embodiments. In some embodiments, charging for QoS is performed in whole or in part by one or more network elements/functions (e.g., service controller, SGSN/GGSN/other gateways, and/or billing interfaces/servers).
In some embodiments, service usage information includes network based service usage information. In some embodiments, the network based service usage information includes network based CDRs. In some embodiments, service usage information includes device based service usage information. In some embodiments, device based service usage information includes device assisted CDRs, also referred to herein as micro-CDRs, as described herein. In some embodiments, micro-CDRs are used for CDR mediation or reconciliation that provides for service usage accounting on any device activity that is desired (e.g., providing granular service usage information, such as based on application layer service usage monitoring, transaction service usage monitoring, QoS activities/sessions/transactions, and/or other types of service usage information). In some embodiments, each device includes a service processor (e.g., a service processor executed on a processor of a communications device, such as a mobile device or an intermediate networking device that can communicate with a wireless network).
In some embodiments, each device activity that is desired to be associated with a billing event (e.g., for a QoS related billing event) is assigned a micro-CDR transaction code, and the service processor is programmed to account for that activity associated with that transaction code (e.g., various transaction codes can be associated with service usage associated with certain services, applications, and/or based on QoS classes or priorities, respectively, which can be used for providing granular service usage for these various Internet/network based services/sites/transactions and/or any other Internet/network based services/sites, which can include transactional based services). For example, using these techniques, as described herein, essentially any type of device activity (e.g., including QoS classes and prioritization) can be individually accounted for and/or controlled (e.g., throttled, restricted, and/or otherwise controlled as desired). In some embodiments, the service processor periodically reports (e.g., during each heartbeat or based on any other periodic, push, and/or pull communication technique(s)) micro-CDR usage measures to, for example, a service controller or some other network element/function. In some embodiments, the service controller reformats the heartbeat micro-CDR usage information into a valid CDR format (e.g., a CDR format that is used and can be processed by an SGSN or GGSN or some other authorized network element/function for CDRs) and then transmits the reformatted micro-CDRs to a network element/function for performing CDR mediation.
In some embodiments, CDR mediation is used to properly account for the micro-CDR service usage information by depositing it into an appropriate service usage account and deducting it from the user device bulk service usage account. For example, this technique provides for a flexible service usage billing solution that uses pre-existing solutions for CDR mediation and billing. For example, the billing system can process the mediated CDR feed from CDR mediation, apply the appropriate account billing codes to the aggregated micro-CDR information that was generated by the device, and then generate billing events in a manner that does not require changes to existing billing systems, infrastructures, and techniques (e.g., using new transaction codes to label the new device assisted billing capabilities).
In some embodiments, the various QoS techniques performed on or by the communications device (e.g., using a service processor to provide or assist in providing QoS session provisioning, QoS policy management, QoS policy enforcement, and/or QoS charging, such as QoS charging records and reports) are verified.
For example, a QoS request, QoS related policy rules (e.g., QoS activity map, QoS related service plan and/or service policy settings) and implementation, QoS policy enforcement, and QoS charging are verified (e.g., periodically, per transaction, and/or based on some other criteria/metric). In some embodiments, verification techniques include one or more of the following: compare a network based service usage measure with a first service policy associated with the communications device, compare a device assisted service usage measure with the first service policy, compare the network based service usage measure to the device assisted service usage measure, perform a test and confirm a device assisted service usage measure based on the test, perform a User Interface (UI) notification (e.g., which can include a user authentication, password, question/answer challenge, and/or other authentication technique) and other similar verification techniques as will now be apparent. Accordingly, in some embodiments, QoS for DAS “closes the loop” for verification of various QoS related techniques, such as QoS requests, QoS grants, QoS usage, and/or QoS charging. In some embodiments, the service processor and the service controller serve as a verifiable QoS management/coordination system for other QoS elements/functions in network. In some embodiments, if such or other verification techniques determine or assist in determining that a QoS request, QoS report, and/or QoS policy behavior does not match expected requests, reports, and/or policy, then responsive actions can be performed, for example, the communications device can be suspended, quarantined and/or flagged for further analysis/scrutiny to determine whether the device is malfunctioning, needs updating, has been tampered with or compromised, is infected with malware, and/or if any other problem exists.
In some embodiments, the communications device (e.g., the service processor) maintains a QoS flow table that associates or maps device activity to QoS level/class to RAB/QoS channel, and in some embodiments, the communications device also informs a QoS management network function/element of the relative priority of the QoS flows for the communications device (e.g., based on or using the QoS flow table). In some embodiments, the service controller receives or collects information from the communications device and maintains such a QoS flow table for the communications device and in some embodiments, the service controller also informs a QoS management network function/element of the relative priority of the QoS flows for the communications device (e.g., based on or using the QoS flow table). In some embodiments, flows can be assigned to activities originating at the communications device in a transparent way, or simply by activity class or user preference or using other techniques.
In some embodiments, the communications device maintains a table of QoS billing rates, scheduled transmission times, and/other QoS related information to implement an overlay MAC at the data networking level to manage QoS on legacy networks that are not QoS MAC enabled and/or do not have the various functionality to support QoS controls (e.g., and such techniques can also be used to provide for QoS functionality across different networks). In some embodiments, QoS related policies are exchanged between roaming and home service controllers to facilitate QoS support while roaming on a non-home network(s).
In some embodiments, the communications device serves as a network capacity indicator (e.g., collecting network capacity information for a local cell and communicating or reporting that network capacity information to the service controller). For example, permanent local cell communications devices can be placed in local cell areas to augment legacy equipment for such network capacity indicator/reporting functions.
In some embodiments, service partners and/or service providers can subsidize in whole or in part to upgrade a given user or group of users to better QoS related service level agreement (SLA)/class for a preferred destination. In some embodiments, based on monitored service usage and/or other monitored behavior of the communications device, such subsidized QoS upgrade/offers can be presented to a user of the communications device (e.g., as an incentive/reward for desired or preferred user behavior or for other reasons).
In some embodiments, QoS charging is based on QoS channel/reservation, service flow, or RAB charging (e.g., single flow per RAB, multi-flow per RAB, multi-RAB per flow). In some embodiments, charging is based on one or more of the following: user service class request, traffic volume and class, time and class, network capacity (e.g., busy state) and class, time of day and class, location, traffic type, application type, application class, destination, destination type, partner service, and/or other criteria/measures. In some embodiments, QoS charging is verified using the various verification techniques described herein (e.g., test charging events). In some embodiments, QoS charging is by data usage (e.g., by Megabyte (MB)), service flow by time by QoS class, speed by time, and/or other criteria/measures.
In some embodiments, QoS for DAS includes coordinating functions with one or more of the following: DAS elements/functions, Radio Access Network (RAN), Transport network, Core network, GRX network, IPX network, and/or other networks/elements/functions.
As shown,
In some embodiments,
In some embodiments, a service provider selects who receives a reconciliation report of activations and usage by service plan type. In some embodiments, service usage information (e.g., based on CDRs and/or micro-CDRs or other service usage measures) are used for service plan billing and for reconciliation reports. In some embodiments, different service plans on the same device (e.g., device 100) can be sent to different partners or the same partner. In some embodiments, multi-device and multi-user reconciliation capabilities are provided. In some embodiments, a settlement platform service is provided. In some embodiments, various revenue share techniques as described herein are provided (e.g., implemented using a settlement platform service, using, for example, service policies and accounting functions 230).
In some embodiments, partitioned device groups are provided. In some embodiments, each partitioned group of devices (e.g., mobile devices 100) can be uniquely managed with secure admin log-ins. In some embodiments, multi-device, multi-user accounting is provided. In some embodiments, capabilities are provided to support multi-party/multi-service reconciliation records to carriers and carrier partners, which can also support various service/transactional revenue share techniques (e.g., for reducing or eliminating the up-front subsidy and associated up-front subsidy risk of certain bounty models). In some embodiments, service usage and profitability analytics are provided (e.g., using aggregated CDRs/micro-CDRs and service policies and accounting functions 230). For example, a partitioned beta test group of devices can be tested and optimized for various service usage policies and/or service plans, and then the optimized service usage policies and/or service plans can be published to an entire or larger device group. In some embodiments, a carrier can be provided a carrier branded device group, and/or a MVNO can be provided a MVNO branded device group.
For example, this provides relatively full featured device based service processor implementation and service controller implementation. As shown, this corresponds to a networking configuration in which the service controller 122 is connected to the Internet 120 and not directly to the access network 1610. As shown, a data plane (e.g., service traffic plane) communication path is shown in solid line connections and control plane (e.g., service control plane) communication path is shown in dashed line connections. As will be apparent, the division in functionality between one device agent and another is based on, for example, design choices, networking environments, devices and/or services/applications, and various different combinations can be used in various different implementations. For example, the functional lines can be re-drawn in any way that the product designers see fit. As shown, this includes certain divisions and functional breakouts for device agents as an illustrative implementation, although other, potentially more complex, embodiments can include different divisions and functional breakouts for device agent functionality specifications, for example, in order to manage development specification and testing complexity and workflow. In addition, the placement of the agents that operate, interact with or monitor the data path can be moved or re-ordered in various embodiments. For example, the functional elements shown in
As shown in
As shown in
In some embodiments, the service control server link 1638 provides for securing, signing, encrypting and/or otherwise protecting the communications before sending such communications over the service control link 1653. For example, the service control server link 1638 can send to the transport layer or directly to the link layer for transmission. In another example, the service control server link 1638 further secures the communications with transport layer encryption, such as TCP TLS or another secure transport layer protocol. As another example, the service control server link 1638 can encrypt at the link layer, such as using IPSEC, various possible VPN services, other forms of IP layer encryption and/or another link layer encryption technique.
As shown in
In some embodiments, the access control integrity server 1654 (and/or some other agent of service controller 122) acts on access control integrity agent 1694 (e.g., service policy security agent) reports and error conditions. Many of the access control integrity agent 1654 checks can be accomplished by the server. For example, the access control integrity agent 1654 checks include one or more of the following: service usage measure against usage range consistent with policies (e.g., usage measure from the network and/or from the device); configuration of agents; operation of the agents; and/or dynamic agent download.
In some embodiments, the access control integrity server 1654 (and/or some other agent of service controller 122) verifies device service policy implementations by comparing various service usage measures (e.g., based on network monitored information, such as by using IPDRs or CDRs, and/or local service usage monitoring information) against expected service usage behavior given the policies that are intended to be in place. For example, device service policy implementations can include measuring total QoS data passed, QoS data passed in a period of time, IP addresses, data per IP address, and/or other measures such as location, downloads, email accessed, URLs, and comparing such measures expected service usage behavior given the policies that are intended to be in place.
In some embodiments, the access control integrity server 1654 (and/or some other agent of service controller 122) verifies device service policy, and the verification error conditions that can indicate a mismatch in QoS service measure and QoS service policy include one or more of the following: unauthorized network access (e.g., access beyond ambient service policy limits); unauthorized network speed (e.g., average speed beyond service policy limit); network data amount does not match QoS policy limit (e.g., device not stop at limit without re-up/revising service policy); unauthorized network address; unauthorized service usage (e.g., VOIP, email, and/or web browsing); unauthorized application usage (e.g., email, VOIP, email, and/or web); service usage rate too high for plan, and policy controller not controlling/throttling it down; and/or any other mismatch in service measure and service policy. Accordingly, in some embodiments, the access control integrity server 1654 (and/or some other agent of service controller 122) provides a policy/service control integrity service to continually (e.g., periodically and/or based on trigger events) verify that the service control of the device has not been compromised and/or is not behaving out of policy.
As shown in
As shown in
In some embodiments, the policy management server 1652 provides adaptive policy management on the device. For example, the policy management server 1652 can issue policy settings and objectives and rely on the device based policy management (e.g., service processor 115) for some or all of the policy adaptation. This approach can require less interaction with the device thereby reducing network chatter on service control link 1653 for purposes of device policy management (e.g., network chatter is reduced relative to various server/network based policy management approaches described above). This approach can also provide robust user privacy embodiments by allowing the user to configure the device policy for user privacy preferences/settings so that, for example, sensitive information (e.g., geo-location data, website history) is not communicated to the network without the user's approval. In some embodiments, the policy management server 1652 adjusts service policy based on time of day. In some embodiments, the policy management server 1652 receives, requests or otherwise obtains a measure of network availability and adjusts traffic shaping policy and/or other policy settings based on available network capacity.
As shown in
As shown in
As shown in
As shown in
As shown in
As shown in
As shown in
As shown in
In some embodiments, the service processor 115 and service controller 122 are capable of assigning multiple service profiles associated with multiple service plans that the user chooses individually or in combination as a package. For example, a device 100 starts with ambient services that include free transaction services wherein the user pays for transactions or events rather than the basic service (e.g., a news service, eReader, PND service, pay as you go session Internet) in which each service is supported with a bill by account capability to correctly account for any subsidized partner billing to provide the transaction services (e.g., Barnes and Noble may pay for the eReader service and offer a revenue share to the service provider for any book or magazine transactions purchased from the device 100). In some embodiments, the bill by account service can also track the transactions and, in some embodiments, advertisements for the purpose of revenue sharing, all using the service monitoring capabilities disclosed herein. After initiating services with the free ambient service discussed above, the user may later choose a post-pay monthly Internet, email and SMS service. In this case, the service controller 122 would obtain from the billing system 123 in the case of network based billing (or in some embodiments the service controller 122 billing event server 1622 in the case of device based billing) the billing plan code for the new Internet, email and SMS service. In some embodiments, this code is cross referenced in a database (e.g., the policy management server 1652) to find the appropriate service profile for the new service in combination with the initial ambient service. The new superset service profile is then applied so that the user maintains free access to the ambient services, and the billing partners continue to subsidize those services, the user also gets access to Internet services and may choose the service control profile (e.g., from one of the embodiments disclosed herein). The superset profile is the profile that provides the combined capabilities of two or more service profiles when the profiles are applied to the same device 100 service processor. In some embodiments, the device 100 (service processor 115) can determine the superset profile rather than the service controller 122 when more than one “stackable” service is selected by the user or otherwise applied to the device. The flexibility of the service processor 115 and service controller 122 embodiments described herein allow for a large variety of service profiles to be defined and applied individually or as a superset to achieve the desired device 100 service features.
As shown in
As shown in
In some embodiments, device assisted services (DAS) techniques for providing an activity map for classifying or categorizing service usage activities to associate various monitored activities (e.g., by URL, by network domain, by website, by network traffic type, by application or application type, and/or any other service usage activity categorization/classification) with associated IP addresses are provided. In some embodiments, a policy control agent (not shown), service monitor agent 1696 (e.g., charging agent), or another agent or function (or combinations thereof) of the service processor 115 provides a DAS activity map. In some embodiments, a policy control agent (not shown), service monitor agent, or another agent or function (or combinations thereof) of the service processor provides an activity map for classifying or categorizing service usage activities to associate various monitored activities (e.g., by Uniform Resource Locator (URL), by network domain, by website, by network traffic type, by application or application type, and/or any other service usage activity classification/categorization) with associated IP addresses. In some embodiments, a policy control agent, service monitor agent, or another agent or function (or combinations thereof) of the service processor determines the associated IP addresses for monitored service usage activities using various techniques to snoop the DNS request(s) (e.g., by performing such snooping techniques on the device 100 the associated IP addresses can be determined without the need for a network request for a reverse DNS lookup). In some embodiments, a policy control agent, service monitor agent, or another agent or function (or combinations thereof) of the service processor records and reports IP addresses or includes a DNS lookup function to report IP addresses or IP addresses and associated URLs for monitored service usage activities. For example, a policy control agent, service monitor agent, or another agent or function (or combinations thereof) of the service processor can determine the associated IP addresses for monitored service usage activities using various techniques to perform a DNS lookup function (e.g., using a local DNS cache on the monitored device 100). In some embodiments, one or more of these techniques are used to dynamically build and maintain a DAS activity map that maps, for example, URLs to IP addresses, applications to IP addresses, content types to IP addresses, and/or any other categorization/classification to IP addresses as applicable. In some embodiments, the DAS activity map is used for various DAS traffic control and/or throttling techniques as described herein with respect to various embodiments. In some embodiments, the DAS activity map is used to provide the user various UI related information and notification techniques related to service usage as described herein with respect to various embodiments. In some embodiments, the DAS activity map is used to provide service usage monitoring, prediction/estimation of future service usage, service usage billing (e.g., bill by account and/or any other service usage/billing categorization techniques), DAS techniques for ambient services usage monitoring, DAS techniques for generating micro-CDRs, and/or any of the various other DAS related techniques as described herein with respect to various embodiments.
In some embodiments, all or a portion of the service processor 115 functions disclosed herein are implemented in software. In some embodiments, all or a portion of the service processor 115 functions are implemented in hardware. In some embodiments, all or substantially all of the service processor 115 functionality (as discussed herein) is implemented and stored in software that can be performed on (e.g., executed by) various components in device 100. In some embodiments, it is advantageous to store or implement certain portions or all of service processor 115 in protected or secure memory so that other undesired programs (and/or unauthorized users) have difficulty accessing the functions or software in service processor 115. In some embodiments, service processor 115, at least in part, is implemented in and/or stored on secure non-volatile memory (e.g., non volatile memory can be secure non-volatile memory) that is not accessible without pass keys and/or other security mechanisms. In some embodiments, the ability to load at least a portion of service processor 115 software into protected non-volatile memory also requires a secure key and/or signature and/or requires that the service processor 115 software components being loaded into non-volatile memory are also securely encrypted and appropriately signed by an authority that is trusted by a secure software downloader function, such as service downloader 1663 as shown in
Referring to
Referring to
Referring to
In some embodiments, QoS techniques as described herein are implemented in the device (e.g., using the service processor 115) and one or more other network elements/functions, such as the BTS 125, service controller 125, RAN, SGSN/GGSN/other gateways and/or other network elements/functions, in which various of the QoS related functions can be distributed or allocated to such network elements/functions based on various design/network architecture approaches as will now be apparent to one of ordinary skill in the art, in which QoS related activities and/or functions at the device 100 are verified using various verification techniques described herein.
In some embodiments, the device determines QoS availability by directly querying QOS link reservation equipment in the network (e.g., an access point, such as the BTS). In some embodiments, the device determines QoS availability based on an intermediate network function that coordinates QoS requests with one or more network QoS link resources. In some embodiments, the device requests a QoS reservation in advance of QOS link establishment with one or more QoS network link resources. In some embodiments, in response to a QoS request, a QoS channel is reported as available only if/after it is determined that the necessary one or more QoS links required to create the QOS channel are available, and, for example, the QoS channel can then be reserved based on a confirmation or automatically be reserved in response to the QoS request.
In some embodiments, the service plan includes a list of activity policies, and each activity policy in the service plan specifies how the activity policy is modified by rules state information. In some embodiments, each activity policy then becomes the instruction for the engine (e.g., QoS mapping function 520) that maps activity policy to QoS activity rules 530. In some embodiments, service controller 122 downloads QoS mapping function 520, which is implemented by service processor 115.
In some embodiments, the service processor determines (e.g., and classifies) application/service usage activity demand with or without granular application/service usage activity (e.g., depending on various user/service plan/service provider/network/legal and/or other privacy restrictions and/or any other related requirements or settings). For example, policies (e.g., service policy settings and/or service profile settings) can be downloaded to provide such application/service usage activity monitoring rules and a QoS activity map for assigning such monitored activities to various QoS classes or priorities, and, in some embodiments, such monitoring and the QoS activity map can also be implemented using various verification techniques described herein (e.g., periodically audited, tested, compared with network service usage information). In some embodiments, the QoS activity map is based on a service plan, service profile, and/or service policy settings associated with the communications device. In some embodiments, the QoS activity map is based on a device group and/or user group. In some embodiments, the QoS activity map is based on user input (e.g., a user of the communications device can identify QoS classes/service levels for various applications and/or service activities, in response to requests for user input, based on user configurations, user defined rules (e.g., to eliminate or mitigate privacy and/or net neutrality concerns/issues), and/or confirmed monitored user behavior QoS related patterns or preferences). In some embodiments, the QoS activity map includes mappings/associations based on one or more of the following: a user preference for a given destination, destination class, application, application class (e.g., by application class instead of with respect to a specific application can also eliminate or mitigate privacy and/or net neutrality concerns/issues), flow, traffic or flow class, time period, time of day, location, network busy state (e.g., provide QoS when you can, then charge more when busy, notify user of busy state), device type, user type, user plan, user group, user standing, partner service, tokens, service type, and/or other criteria or measures.
In some embodiments, various techniques described herein are managed for device 100 for incoming and/or outgoing QoS requests. In some embodiments, as shown in
In some embodiments, the service monitor agent and/or other agents implement virtual traffic tagging by tracking or tracing packet flows through the various communication stack formatting, processing and encryption steps, and providing the virtual tag information to the various agents that monitor, control, shape, throttle or otherwise observe, manipulate or modify the traffic. This tagging approach is referred to herein as virtual tagging, because there is not a literal data flow, traffic flow or packet tag that is attached to flows or packets, and the book-keeping to tag the packet is done through tracking or tracing the flow or packet through the stack instead. In some embodiments, the application interface and/or other agents identify a traffic flow, associate it with a service usage activity and cause a literal tag to be attached to the traffic or packets associated with the activity. This tagging approach is referred to herein as literal tagging. There are various advantages with both the virtual tagging and the literal tagging approaches. For example, it can be preferable in some embodiments to reduce the inter-agent communication required to track or trace a packet through the stack processing by assigning a literal tag so that each flow or packet has its own activity association embedded in the data. As another example, it can be preferable in some embodiments to re-use portions of standard communication stack software or components, enhancing the verifiable traffic control or service control capabilities of the standard stack by inserting additional processing steps associated with the various service agents and monitoring points rather than re-writing the entire stack to correctly process literal tagging information, and in such cases, a virtual tagging scheme may be desired. As yet another example, some standard communication stacks provide for unused, unspecified or otherwise available bit fields in a packet frame or flow, and these unused, unspecified or otherwise available bit fields can be used to literally tag traffic without the need to re-write all of the standard communication stack software, with only the portions of the stack that are added to enhance the verifiable traffic control or service control capabilities of the standard stack needing to decode and use the literal tagging information encapsulated in the available bit fields. In the case of literal tagging, in some embodiments, the tags are removed prior to passing the packets or flows to the network or to the applications utilizing the stack. In some embodiments, the manner in which the virtual or literal tagging is implemented can be developed into a communication standard specification so that various device or service product developers can independently develop the communication stack and/or service processor hardware and/or software in a manner that is compatible with the service controller specifications and the products of other device or service product developers.
It will be appreciated that although the implementation/use of any or all of the measurement points illustrated in
Referring to
As shown in
As shown in
Referring to
Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details provided. There are many alternative ways of implementing the invention. The disclosed embodiments are illustrative and not restrictive.
This application is a continuation of application Ser. No. 12/695,021, entitled QUALITY OF SERVICE FOR DEVICE ASSISTED SERVICES, filed Jan. 27, 2010, which is a continuation-in-part of application Ser. No. 12/380,780, entitled AUTOMATED DEVICE PROVISIONING AND ACTIVATION, filed Mar. 2, 2009, which is incorporated herein by reference for all purposes. Application Ser. No. 12/695,021, entitled QUALITY OF SERVICE FOR DEVICE ASSISTED SERVICES, filed Jan. 27, 2010, claims the benefit of provisional Application No. 61/206,354, entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD, filed Jan. 28, 2009; provisional Application No. 61/206,944, entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD, filed Feb. 4, 2009; provisional Application No. 61/207,393, entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD, filed Feb. 10, 2009; provisional Application No. 61/207,739, entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD, filed Feb. 13, 2009; provisional Application No. 61/252,151, entitled SECURITY TECHNIQUES FOR DEVICE ASSISTED SERVICES, filed Oct. 15, 2009; and provisional Application No. 61/252,153, entitled DEVICE GROUP PARTITIONS AND SETTLEMENT PLATFORM, filed Oct. 15, 2009, all of which are incorporated herein by reference for all purposes. Application Ser. No. 12/380,780, entitled AUTOMATED DEVICE PROVISIONING AND ACTIVATION, filed Mar. 2, 2009, claims the benefit of provisional Application No. 61/206,354, entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD, filed Jan. 28, 2009; provisional Application No. 61/206,944, entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD, filed Feb. 4, 2009; provisional Application No. 61/207,393, entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD filed Feb. 10, 2009; and provisional Application No. 61/207,739, entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD, filed Feb. 13, 2009, all of which are incorporated herein by reference for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
5131020 | Liebesny et al. | Jul 1992 | A |
5283904 | Carson et al. | Feb 1994 | A |
5325532 | Crosswy et al. | Jun 1994 | A |
5572528 | Shuen | Nov 1996 | A |
5577100 | McGregor et al. | Nov 1996 | A |
5594777 | Makkonen et al. | Jan 1997 | A |
5630159 | Zancho | May 1997 | A |
5633484 | Zancho et al. | May 1997 | A |
5754953 | Briancon et al. | May 1998 | A |
5774532 | Gottlieb et al. | Jun 1998 | A |
5794142 | Vanttila et al. | Aug 1998 | A |
5814798 | Zancho | Sep 1998 | A |
5889477 | Fastenrath | Mar 1999 | A |
5892900 | Ginter et al. | Apr 1999 | A |
5903845 | Buhrmann et al. | May 1999 | A |
5915008 | Dulman | Jun 1999 | A |
5933778 | Buhrmann et al. | Aug 1999 | A |
5940472 | Newman et al. | Aug 1999 | A |
5974439 | Bollella | Oct 1999 | A |
5983270 | Abraham et al. | Nov 1999 | A |
6035281 | Crosskey et al. | Mar 2000 | A |
6038452 | Strawczynski et al. | Mar 2000 | A |
6038540 | Krist et al. | Mar 2000 | A |
6047268 | Bartoli et al. | Apr 2000 | A |
6058434 | Wilt et al. | May 2000 | A |
6064878 | Denker et al. | May 2000 | A |
6078953 | Vaid et al. | Jun 2000 | A |
6081591 | Skoog | Jun 2000 | A |
6098878 | Dent et al. | Aug 2000 | A |
6104700 | Haddock et al. | Aug 2000 | A |
6119933 | Wong et al. | Sep 2000 | A |
6125391 | Meltzer et al. | Sep 2000 | A |
6141686 | Jackowski et al. | Oct 2000 | A |
6148336 | Thomas et al. | Nov 2000 | A |
6154738 | Call | Nov 2000 | A |
6185576 | McIntosh | Feb 2001 | B1 |
6198915 | McGregor et al. | Mar 2001 | B1 |
6226277 | Chuah | May 2001 | B1 |
6263055 | Garland et al. | Jul 2001 | B1 |
6292828 | Williams | Sep 2001 | B1 |
6317584 | Abu-Amara et al. | Nov 2001 | B1 |
6381316 | Joyce et al. | Apr 2002 | B2 |
6393014 | Daly et al. | May 2002 | B1 |
6397259 | Lincke et al. | May 2002 | B1 |
6418147 | Wiedeman | Jul 2002 | B1 |
6438575 | Khan et al. | Aug 2002 | B1 |
6445777 | Clark | Sep 2002 | B1 |
6449479 | Sanchez | Sep 2002 | B1 |
6477670 | Ahmadvand | Nov 2002 | B1 |
6502131 | Vaid et al. | Dec 2002 | B1 |
6505114 | Luciani | Jan 2003 | B2 |
6532235 | Benson et al. | Mar 2003 | B1 |
6532579 | Sato et al. | Mar 2003 | B2 |
6539082 | Lowe et al. | Mar 2003 | B1 |
6542992 | Peirce et al. | Apr 2003 | B1 |
6563806 | Yano et al. | May 2003 | B1 |
6574321 | Cox et al. | Jun 2003 | B1 |
6574465 | Marsh et al. | Jun 2003 | B2 |
6578076 | Putzolu | Jun 2003 | B1 |
6581092 | Motoyama et al. | Jun 2003 | B1 |
6598034 | Kloth | Jul 2003 | B1 |
6603969 | Vuoristo et al. | Aug 2003 | B1 |
6606744 | Mikurak | Aug 2003 | B1 |
6628934 | Rosenberg et al. | Sep 2003 | B2 |
6631122 | Arunachalam et al. | Oct 2003 | B1 |
6639975 | O'Neal et al. | Oct 2003 | B1 |
6640097 | Corrigan et al. | Oct 2003 | B2 |
6640334 | Rasmussen | Oct 2003 | B1 |
6650887 | McGregor et al. | Nov 2003 | B2 |
6651101 | Gai et al. | Nov 2003 | B1 |
6654814 | Britton et al. | Nov 2003 | B1 |
6658254 | Purdy et al. | Dec 2003 | B1 |
6662014 | Walsh | Dec 2003 | B1 |
6678516 | Nordman et al. | Jan 2004 | B2 |
6683853 | Kannas et al. | Jan 2004 | B1 |
6684244 | Goldman et al. | Jan 2004 | B1 |
6697821 | Ziff et al. | Feb 2004 | B2 |
6725031 | Watler et al. | Apr 2004 | B2 |
6735206 | Oki et al. | May 2004 | B1 |
6748195 | Phillips | Jun 2004 | B1 |
6748437 | Mankude et al. | Jun 2004 | B1 |
6754470 | Hendrickson et al. | Jun 2004 | B2 |
6757717 | Goldstein | Jun 2004 | B1 |
6763000 | Walsh | Jul 2004 | B1 |
6763226 | McZeal, Jr. | Jul 2004 | B1 |
6765864 | Natarajan et al. | Jul 2004 | B1 |
6765925 | Sawyer et al. | Jul 2004 | B1 |
6782412 | Brophy et al. | Aug 2004 | B2 |
6785889 | Williams | Aug 2004 | B1 |
6829596 | Frazee | Dec 2004 | B1 |
6829696 | Balmer et al. | Dec 2004 | B1 |
6839340 | Voit et al. | Jan 2005 | B1 |
6873988 | Herrmann et al. | Mar 2005 | B2 |
6876653 | Ambe et al. | Apr 2005 | B2 |
6882718 | Smith | Apr 2005 | B1 |
6885997 | Roberts | Apr 2005 | B1 |
6901440 | Bimm et al. | May 2005 | B1 |
6920455 | Weschler | Jul 2005 | B1 |
6922562 | Ward et al. | Jul 2005 | B2 |
6928280 | Xanthos et al. | Aug 2005 | B1 |
6934249 | Bertin et al. | Aug 2005 | B1 |
6947723 | Gurnani et al. | Sep 2005 | B1 |
6952428 | Necka et al. | Oct 2005 | B1 |
6957067 | Iyer et al. | Oct 2005 | B1 |
6965667 | Trabandt et al. | Nov 2005 | B2 |
6965872 | Grdina | Nov 2005 | B1 |
6967958 | Ono et al. | Nov 2005 | B2 |
6970692 | Tysor | Nov 2005 | B2 |
6982733 | McNally et al. | Jan 2006 | B1 |
6983370 | Eaton et al. | Jan 2006 | B2 |
6996076 | Forbes et al. | Feb 2006 | B1 |
6996393 | Pyhalammi et al. | Feb 2006 | B2 |
6998985 | Reisman et al. | Feb 2006 | B2 |
7002920 | Ayyagari et al. | Feb 2006 | B1 |
7007295 | Rose et al. | Feb 2006 | B1 |
7013469 | Smith et al. | Mar 2006 | B2 |
7017189 | DeMello et al. | Mar 2006 | B1 |
7024200 | McKenna et al. | Apr 2006 | B2 |
7024460 | Koopmas et al. | Apr 2006 | B2 |
7027408 | Nabkel et al. | Apr 2006 | B2 |
7032072 | Quinn et al. | Apr 2006 | B1 |
7039027 | Bridgelall | May 2006 | B2 |
7039037 | Wang et al. | May 2006 | B2 |
7039403 | Wong | May 2006 | B2 |
7039713 | Van Gunter et al. | May 2006 | B1 |
7042988 | Juitt et al. | May 2006 | B2 |
7043226 | Yamauchi | May 2006 | B2 |
7043268 | Yukie et al. | May 2006 | B2 |
7047276 | Liu et al. | May 2006 | B2 |
7058022 | Carolan et al. | Jun 2006 | B1 |
7058968 | Rowland et al. | Jun 2006 | B2 |
7068600 | Cain | Jun 2006 | B2 |
7069248 | Huber | Jun 2006 | B2 |
7084775 | Smith | Aug 2006 | B1 |
7092696 | Hosain et al. | Aug 2006 | B1 |
7102620 | Harries et al. | Sep 2006 | B2 |
7113780 | McKenna et al. | Sep 2006 | B2 |
7113997 | Jayapalan et al. | Sep 2006 | B2 |
7133695 | Beyda | Nov 2006 | B2 |
7139569 | Kato | Nov 2006 | B2 |
7142876 | Trossen et al. | Nov 2006 | B2 |
7149229 | Leung | Dec 2006 | B1 |
7149521 | Sundar et al. | Dec 2006 | B2 |
7158792 | Cook et al. | Jan 2007 | B1 |
7162237 | Silver et al. | Jan 2007 | B1 |
7167078 | Pourchot | Jan 2007 | B2 |
7174174 | Boris et al. | Feb 2007 | B2 |
7180855 | Lin | Feb 2007 | B1 |
7181017 | Nagel et al. | Feb 2007 | B1 |
7197321 | Erskine et al. | Mar 2007 | B2 |
7200112 | Sundar et al. | Apr 2007 | B2 |
7203169 | Okholm et al. | Apr 2007 | B1 |
7203752 | Rice et al. | Apr 2007 | B2 |
7212491 | Koga | May 2007 | B2 |
7222190 | Klinker et al. | May 2007 | B2 |
7222304 | Beaton et al. | May 2007 | B2 |
7224968 | Dobson et al. | May 2007 | B2 |
7228354 | Chambliss et al. | Jun 2007 | B2 |
7236780 | Benco et al. | Jun 2007 | B2 |
7242668 | Kan et al. | Jul 2007 | B2 |
7242920 | Morris | Jul 2007 | B2 |
7245901 | McGregor et al. | Jul 2007 | B2 |
7248570 | Bahl et al. | Jul 2007 | B2 |
7251218 | Jorgensen | Jul 2007 | B2 |
7260382 | Lamb et al. | Aug 2007 | B1 |
7266371 | Amin et al. | Sep 2007 | B1 |
7271765 | Stilp et al. | Sep 2007 | B2 |
7280816 | Fratti et al. | Oct 2007 | B2 |
7280818 | Clayton | Oct 2007 | B2 |
7283561 | Picher-Dempsey | Oct 2007 | B1 |
7283963 | Fitzpatrick et al. | Oct 2007 | B1 |
7286834 | Walter | Oct 2007 | B2 |
7286848 | Vireday et al. | Oct 2007 | B2 |
7289489 | Kung et al. | Oct 2007 | B1 |
7290283 | Copeland, III | Oct 2007 | B2 |
7310424 | Gehring et al. | Dec 2007 | B2 |
7313237 | Bahl et al. | Dec 2007 | B2 |
7317699 | Godfrey et al. | Jan 2008 | B2 |
7318111 | Zhao | Jan 2008 | B2 |
7320029 | Rinne et al. | Jan 2008 | B2 |
7322044 | Hrastar | Jan 2008 | B2 |
7324447 | Morford | Jan 2008 | B1 |
7325037 | Lawson | Jan 2008 | B2 |
7336960 | Zavalkovsky et al. | Feb 2008 | B2 |
7346410 | Uchiyama | Mar 2008 | B2 |
7349695 | Oommen et al. | Mar 2008 | B2 |
7353533 | Wright et al. | Apr 2008 | B2 |
7356011 | Waters et al. | Apr 2008 | B1 |
7356337 | Florence | Apr 2008 | B2 |
7366497 | Nagata | Apr 2008 | B2 |
7366654 | Moore | Apr 2008 | B2 |
7373136 | Watler et al. | May 2008 | B2 |
7373179 | Stine et al. | May 2008 | B2 |
7379731 | Natsuno et al. | May 2008 | B2 |
7388950 | Elsey et al. | Jun 2008 | B2 |
7391724 | Alakoski et al. | Jun 2008 | B2 |
7395244 | Kingsford | Jul 2008 | B1 |
7401338 | Bowen et al. | Jul 2008 | B1 |
7403763 | Maes | Jul 2008 | B2 |
7409447 | Assadzadeh | Aug 2008 | B1 |
7411930 | Montojo et al. | Aug 2008 | B2 |
7418253 | Kavanah | Aug 2008 | B2 |
7418257 | Kim | Aug 2008 | B2 |
7421004 | Feher | Sep 2008 | B2 |
7444669 | Bahl et al. | Oct 2008 | B1 |
7450591 | Korling et al. | Nov 2008 | B2 |
7450927 | Creswell et al. | Nov 2008 | B1 |
7454191 | Dawson et al. | Nov 2008 | B2 |
7457265 | Julka et al. | Nov 2008 | B2 |
7457870 | Lownsbrough et al. | Nov 2008 | B1 |
7460837 | Diener | Dec 2008 | B2 |
7472189 | Mallya et al. | Dec 2008 | B2 |
7478420 | Wright et al. | Jan 2009 | B2 |
7486185 | Culpepper et al. | Feb 2009 | B2 |
7493659 | Wu et al. | Feb 2009 | B1 |
7496652 | Pezzutti | Feb 2009 | B2 |
7499438 | Hinman et al. | Mar 2009 | B2 |
7499537 | Elsey et al. | Mar 2009 | B2 |
7502672 | Kolls | Mar 2009 | B1 |
7508799 | Sumner et al. | Mar 2009 | B2 |
7512128 | DiMambro et al. | Mar 2009 | B2 |
7515608 | Yuan et al. | Apr 2009 | B2 |
7515926 | Bu et al. | Apr 2009 | B2 |
7516219 | Moghaddam et al. | Apr 2009 | B2 |
7529204 | Bourlas et al. | May 2009 | B2 |
7535880 | Hinman et al. | May 2009 | B1 |
7536695 | Alam et al. | May 2009 | B2 |
7539132 | Werner et al. | May 2009 | B2 |
7540408 | Levine et al. | Jun 2009 | B2 |
7545782 | Rayment et al. | Jun 2009 | B2 |
7546460 | Maes | Jun 2009 | B2 |
7546629 | Albert et al. | Jun 2009 | B2 |
7548976 | Bahl et al. | Jun 2009 | B2 |
7551922 | Roskowski et al. | Jun 2009 | B2 |
7554983 | Muppala | Jun 2009 | B1 |
7555757 | Smith et al. | Jun 2009 | B2 |
7561899 | Lee | Jul 2009 | B2 |
7564799 | Holland et al. | Jul 2009 | B2 |
7565141 | Macaluso | Jul 2009 | B2 |
7574509 | Nixon et al. | Aug 2009 | B2 |
7574731 | Fascenda | Aug 2009 | B2 |
7580356 | Mishra et al. | Aug 2009 | B1 |
7580857 | VanFleet et al. | Aug 2009 | B2 |
7583964 | Wong | Sep 2009 | B2 |
7586871 | Hamilton et al. | Sep 2009 | B2 |
7593417 | Wang et al. | Sep 2009 | B2 |
7593730 | Khandelwal et al. | Sep 2009 | B2 |
7596373 | Mcgregor et al. | Sep 2009 | B2 |
7599288 | Cole et al. | Oct 2009 | B2 |
7609650 | Roskowski et al. | Oct 2009 | B2 |
7609700 | Ying et al. | Oct 2009 | B1 |
7610328 | Haase et al. | Oct 2009 | B2 |
7610396 | Taglienti et al. | Oct 2009 | B2 |
7614051 | Glaum et al. | Nov 2009 | B2 |
7616962 | Oswal et al. | Nov 2009 | B2 |
7617516 | Huslak et al. | Nov 2009 | B2 |
7620041 | Dunn et al. | Nov 2009 | B2 |
7620065 | Falardeau | Nov 2009 | B2 |
7620162 | Aaron et al. | Nov 2009 | B2 |
7627314 | Carlson et al. | Dec 2009 | B2 |
7627767 | Sherman et al. | Dec 2009 | B2 |
7627872 | Hebeler et al. | Dec 2009 | B2 |
7633438 | Tysowski | Dec 2009 | B2 |
7634388 | Archer et al. | Dec 2009 | B2 |
7636574 | Poosala | Dec 2009 | B2 |
7644151 | Jerrim et al. | Jan 2010 | B2 |
7644267 | Ylikoski et al. | Jan 2010 | B2 |
7647047 | Moghaddam et al. | Jan 2010 | B2 |
7650137 | Jobs et al. | Jan 2010 | B2 |
7653394 | McMillin | Jan 2010 | B2 |
7668176 | Chuah | Feb 2010 | B2 |
7668612 | Okkonen | Feb 2010 | B1 |
7668903 | Edwards et al. | Feb 2010 | B2 |
7676673 | Weller et al. | Mar 2010 | B2 |
7684370 | Kezys | Mar 2010 | B2 |
7685131 | Batra et al. | Mar 2010 | B2 |
7685254 | Pandya | Mar 2010 | B2 |
7685530 | Sherrard et al. | Mar 2010 | B2 |
7693720 | Kennewick et al. | Apr 2010 | B2 |
7697540 | Haddad et al. | Apr 2010 | B2 |
7710932 | Muthuswamy et al. | May 2010 | B2 |
7711848 | Maes | May 2010 | B2 |
7720464 | Batta | May 2010 | B2 |
7720505 | Gopi et al. | May 2010 | B2 |
7720960 | Pruss et al. | May 2010 | B2 |
7725570 | Lewis | May 2010 | B1 |
7729326 | Sekhar | Jun 2010 | B2 |
7730123 | Erickson et al. | Jun 2010 | B1 |
7734784 | Araujo et al. | Jun 2010 | B1 |
7742406 | Muppala | Jun 2010 | B1 |
7746854 | Ambe et al. | Jun 2010 | B2 |
7747240 | Briscoe et al. | Jun 2010 | B1 |
7747699 | Prueitt et al. | Jun 2010 | B2 |
7747730 | Harlow | Jun 2010 | B1 |
7752330 | Olsen et al. | Jul 2010 | B2 |
7756056 | Kim et al. | Jul 2010 | B2 |
7756534 | Anupam et al. | Jul 2010 | B2 |
7756757 | Oakes, III | Jul 2010 | B1 |
7760137 | Martucci et al. | Jul 2010 | B2 |
7760711 | Kung et al. | Jul 2010 | B1 |
7760861 | Croak et al. | Jul 2010 | B1 |
7774323 | Helfman | Aug 2010 | B2 |
7774456 | Lownsbrough et al. | Aug 2010 | B1 |
7778176 | Morford | Aug 2010 | B2 |
7778643 | Laroia et al. | Aug 2010 | B2 |
7792257 | Vanier et al. | Sep 2010 | B1 |
7792538 | Kozisek | Sep 2010 | B2 |
7792708 | Alva | Sep 2010 | B2 |
7797060 | Grgic et al. | Sep 2010 | B2 |
7797204 | Balent | Sep 2010 | B2 |
7797401 | Stewart et al. | Sep 2010 | B2 |
7801523 | Kenderov | Sep 2010 | B1 |
7801783 | Kende et al. | Sep 2010 | B2 |
7801985 | Pitkow et al. | Sep 2010 | B1 |
7802724 | Nohr | Sep 2010 | B1 |
7805140 | Friday et al. | Sep 2010 | B2 |
7805606 | Birger et al. | Sep 2010 | B2 |
7809351 | Panda et al. | Oct 2010 | B1 |
7817615 | Breau et al. | Oct 2010 | B1 |
7822837 | Urban et al. | Oct 2010 | B1 |
7826427 | Sood et al. | Nov 2010 | B2 |
7826607 | De Carvalho Resende et al. | Nov 2010 | B1 |
7843843 | Papp, III et al. | Nov 2010 | B1 |
7844034 | Oh et al. | Nov 2010 | B1 |
7844728 | Anderson et al. | Nov 2010 | B2 |
7848768 | Omori et al. | Dec 2010 | B2 |
7849161 | Koch et al. | Dec 2010 | B2 |
7849477 | Cristofalo et al. | Dec 2010 | B2 |
7853255 | Karaoguz et al. | Dec 2010 | B2 |
7856226 | Wong et al. | Dec 2010 | B2 |
7860088 | Lioy | Dec 2010 | B2 |
7865182 | Macaluso | Jan 2011 | B2 |
7865187 | Ramer et al. | Jan 2011 | B2 |
7868778 | Kenwright | Jan 2011 | B2 |
7873344 | Bowser et al. | Jan 2011 | B2 |
7873705 | Kalish | Jan 2011 | B2 |
7877090 | Maes | Jan 2011 | B2 |
7881199 | Krstulich | Feb 2011 | B2 |
7881697 | Baker et al. | Feb 2011 | B2 |
7882029 | White | Feb 2011 | B2 |
7886047 | Potluri | Feb 2011 | B1 |
7889384 | Armentrout et al. | Feb 2011 | B2 |
7890084 | Dudziak et al. | Feb 2011 | B1 |
7890111 | Bugenhagen | Feb 2011 | B2 |
7894431 | Goring et al. | Feb 2011 | B2 |
7899039 | Andreasen et al. | Mar 2011 | B2 |
7899438 | Baker et al. | Mar 2011 | B2 |
7903553 | Liu | Mar 2011 | B2 |
7907970 | Park et al. | Mar 2011 | B2 |
7911975 | Droz et al. | Mar 2011 | B2 |
7912025 | Pattenden et al. | Mar 2011 | B2 |
7912056 | Brassem | Mar 2011 | B1 |
7920529 | Mahler et al. | Apr 2011 | B1 |
7921463 | Sood et al. | Apr 2011 | B2 |
7925778 | Wijnands et al. | Apr 2011 | B1 |
7929959 | DeAtley et al. | Apr 2011 | B2 |
7929960 | Martin et al. | Apr 2011 | B2 |
7929973 | Zavalkovsky et al. | Apr 2011 | B2 |
7930327 | Craft et al. | Apr 2011 | B2 |
7930446 | Kesselman et al. | Apr 2011 | B2 |
7933274 | Verma et al. | Apr 2011 | B2 |
7936736 | Proctor, Jr. et al. | May 2011 | B2 |
7937069 | Rassam | May 2011 | B2 |
7937450 | Janik | May 2011 | B2 |
7940685 | Breslau et al. | May 2011 | B1 |
7940751 | Hansen | May 2011 | B2 |
7941184 | Prendergast et al. | May 2011 | B2 |
7944948 | Chow et al. | May 2011 | B2 |
7945238 | Baker et al. | May 2011 | B2 |
7945240 | Klock et al. | May 2011 | B1 |
7945945 | Graham et al. | May 2011 | B2 |
7948952 | Hurtta et al. | May 2011 | B2 |
7948953 | Melkote et al. | May 2011 | B2 |
7948968 | Voit et al. | May 2011 | B2 |
7949529 | Weider et al. | May 2011 | B2 |
7953808 | Sharp et al. | May 2011 | B2 |
7953877 | Vemula et al. | May 2011 | B2 |
7957020 | Mine et al. | Jun 2011 | B2 |
7957381 | Clermidy et al. | Jun 2011 | B2 |
7957511 | Drudis et al. | Jun 2011 | B2 |
7958029 | Bobich et al. | Jun 2011 | B1 |
7962622 | Friend et al. | Jun 2011 | B2 |
7965983 | Swan et al. | Jun 2011 | B1 |
7966405 | Sundaresan et al. | Jun 2011 | B2 |
7969950 | Iyer et al. | Jun 2011 | B2 |
7970350 | Sheynman et al. | Jun 2011 | B2 |
7970426 | Poe et al. | Jun 2011 | B2 |
7974624 | Gallagher et al. | Jul 2011 | B2 |
7975184 | Goff et al. | Jul 2011 | B2 |
7978627 | Taylor et al. | Jul 2011 | B2 |
7978686 | Goyal et al. | Jul 2011 | B2 |
7984130 | Bogineni et al. | Jul 2011 | B2 |
7984511 | Kocher et al. | Jul 2011 | B2 |
7986935 | D'Souza et al. | Jul 2011 | B1 |
7987496 | Bryce et al. | Jul 2011 | B2 |
7987510 | Kocher et al. | Jul 2011 | B2 |
7990049 | Shioya | Aug 2011 | B2 |
8000276 | Scherzer et al. | Aug 2011 | B2 |
8000318 | Wiley et al. | Aug 2011 | B2 |
8005009 | McKee et al. | Aug 2011 | B2 |
8005459 | Balsillie | Aug 2011 | B2 |
8005726 | Bao | Aug 2011 | B1 |
8005988 | Maes | Aug 2011 | B2 |
8010080 | Thenthiruperai et al. | Aug 2011 | B1 |
8010081 | Roskowski | Aug 2011 | B1 |
8010082 | Sutaria et al. | Aug 2011 | B2 |
8015133 | Wu et al. | Sep 2011 | B1 |
8015234 | Lum et al. | Sep 2011 | B2 |
8019687 | Wang et al. | Sep 2011 | B2 |
8019820 | Son et al. | Sep 2011 | B2 |
8019846 | Roelens et al. | Sep 2011 | B2 |
8019868 | Rao et al. | Sep 2011 | B2 |
8019886 | Harrang et al. | Sep 2011 | B2 |
8023425 | Raleigh | Sep 2011 | B2 |
8024397 | Erickson et al. | Sep 2011 | B1 |
8027339 | Short et al. | Sep 2011 | B2 |
8031601 | Feroz et al. | Oct 2011 | B2 |
8032168 | Ikaheimo | Oct 2011 | B2 |
8032409 | Mikurak | Oct 2011 | B1 |
8032899 | Archer et al. | Oct 2011 | B2 |
8036600 | Garrett et al. | Oct 2011 | B2 |
8045973 | Chambers | Oct 2011 | B2 |
8046449 | Yoshiuchi | Oct 2011 | B2 |
8050275 | Iyer | Nov 2011 | B1 |
8050690 | Neeraj | Nov 2011 | B2 |
8050705 | Sicher et al. | Nov 2011 | B2 |
8059530 | Cole | Nov 2011 | B1 |
8060463 | Spiegel | Nov 2011 | B1 |
8064418 | Maki | Nov 2011 | B2 |
8064896 | Bell et al. | Nov 2011 | B2 |
8068824 | Shan et al. | Nov 2011 | B2 |
8068829 | Lemond et al. | Nov 2011 | B2 |
8073427 | Koch et al. | Dec 2011 | B2 |
8073721 | Lewis | Dec 2011 | B1 |
8078140 | Baker et al. | Dec 2011 | B2 |
8078163 | Lemond et al. | Dec 2011 | B2 |
8086398 | Sanchez et al. | Dec 2011 | B2 |
8086497 | Oakes, III | Dec 2011 | B1 |
8086791 | Caulkins | Dec 2011 | B2 |
8090359 | Proctor, Jr. et al. | Jan 2012 | B2 |
8090616 | Proctor, Jr. et al. | Jan 2012 | B2 |
8094551 | Huber et al. | Jan 2012 | B2 |
8095112 | Chow et al. | Jan 2012 | B2 |
8095124 | Balia | Jan 2012 | B2 |
8095640 | Guingo et al. | Jan 2012 | B2 |
8095666 | Schmidt et al. | Jan 2012 | B2 |
8098579 | Ray et al. | Jan 2012 | B2 |
8099077 | Chowdhury et al. | Jan 2012 | B2 |
8099517 | Jia et al. | Jan 2012 | B2 |
8102814 | Rahman et al. | Jan 2012 | B2 |
8103285 | Kalhan | Jan 2012 | B2 |
8104080 | Burns et al. | Jan 2012 | B2 |
8107953 | Zimmerman et al. | Jan 2012 | B2 |
8108520 | Ruutu et al. | Jan 2012 | B2 |
8112435 | Epstein et al. | Feb 2012 | B2 |
8116223 | Tian et al. | Feb 2012 | B2 |
8116749 | Proctor, Jr. et al. | Feb 2012 | B2 |
8116781 | Chen et al. | Feb 2012 | B2 |
8122128 | Burke, II et al. | Feb 2012 | B2 |
8122249 | Falk et al. | Feb 2012 | B2 |
8126123 | Cai et al. | Feb 2012 | B2 |
8126396 | Bennett | Feb 2012 | B2 |
8126476 | Vardi et al. | Feb 2012 | B2 |
8126722 | Robb et al. | Feb 2012 | B2 |
8130793 | Edwards et al. | Mar 2012 | B2 |
8131256 | Martti et al. | Mar 2012 | B2 |
8131281 | Hildner et al. | Mar 2012 | B1 |
8131840 | Denker | Mar 2012 | B1 |
8134954 | Godfrey et al. | Mar 2012 | B2 |
8135388 | Gailloux et al. | Mar 2012 | B1 |
8135392 | Marcellino et al. | Mar 2012 | B2 |
8135657 | Kapoor et al. | Mar 2012 | B2 |
8144591 | Ghai et al. | Mar 2012 | B2 |
8149823 | Turcan et al. | Apr 2012 | B2 |
8150394 | Bianconi et al. | Apr 2012 | B2 |
8150431 | Wolovitz et al. | Apr 2012 | B2 |
8155155 | Chow et al. | Apr 2012 | B1 |
8155620 | Wang et al. | Apr 2012 | B2 |
8155666 | Alizadeh-Shabdiz | Apr 2012 | B2 |
8155670 | Fullam et al. | Apr 2012 | B2 |
8156206 | Kiley et al. | Apr 2012 | B2 |
8160015 | Rashid et al. | Apr 2012 | B2 |
8160598 | Savoor | Apr 2012 | B2 |
8165576 | Raju et al. | Apr 2012 | B2 |
8166040 | Brindisi et al. | Apr 2012 | B2 |
8166554 | John | Apr 2012 | B2 |
8170553 | Bennett | May 2012 | B2 |
8174378 | Richman et al. | May 2012 | B2 |
8174970 | Adamczyk et al. | May 2012 | B2 |
8175574 | Panda et al. | May 2012 | B1 |
8180881 | Seo et al. | May 2012 | B2 |
8180886 | Overcash et al. | May 2012 | B2 |
8184530 | Swan et al. | May 2012 | B1 |
8184590 | Rosenblatt | May 2012 | B2 |
8185088 | Klein et al. | May 2012 | B2 |
8185093 | Jheng et al. | May 2012 | B2 |
8185127 | Cai et al. | May 2012 | B1 |
8185152 | Goldner | May 2012 | B1 |
8185158 | Tamura et al. | May 2012 | B2 |
8190122 | Alexander et al. | May 2012 | B1 |
8190675 | Tribbett | May 2012 | B2 |
8191116 | Gazzard | May 2012 | B1 |
8191124 | Wynn et al. | May 2012 | B2 |
8194549 | Huber et al. | Jun 2012 | B2 |
8194553 | Liang et al. | Jun 2012 | B2 |
8194572 | Horvath et al. | Jun 2012 | B2 |
8195093 | Garrett et al. | Jun 2012 | B2 |
8195163 | Gisby et al. | Jun 2012 | B2 |
8195661 | Kalavade | Jun 2012 | B2 |
8196199 | Hrastar et al. | Jun 2012 | B2 |
8200163 | Hoffman | Jun 2012 | B2 |
8200200 | Belser et al. | Jun 2012 | B1 |
8200509 | Kenedy et al. | Jun 2012 | B2 |
8200775 | Moore | Jun 2012 | B2 |
8200818 | Freund et al. | Jun 2012 | B2 |
8204190 | Bang et al. | Jun 2012 | B2 |
8204505 | Jin et al. | Jun 2012 | B2 |
8208788 | Ando et al. | Jun 2012 | B2 |
8208919 | Kotecha | Jun 2012 | B2 |
8213296 | Shannon et al. | Jul 2012 | B2 |
8213363 | Ying et al. | Jul 2012 | B2 |
8214536 | Zhao | Jul 2012 | B2 |
8223741 | Bartlett et al. | Jul 2012 | B1 |
8224382 | Bultman | Jul 2012 | B2 |
8224773 | Spiegel | Jul 2012 | B2 |
8228818 | Chase et al. | Jul 2012 | B2 |
8229394 | Karlberg | Jul 2012 | B2 |
8229914 | Ramer et al. | Jul 2012 | B2 |
8233433 | Kalhan | Jul 2012 | B2 |
8233883 | De Froment | Jul 2012 | B2 |
8233895 | Tysowski | Jul 2012 | B2 |
8238287 | Gopi et al. | Aug 2012 | B1 |
8239520 | Grah | Aug 2012 | B2 |
8242959 | Mia et al. | Aug 2012 | B2 |
8244241 | Montemurro | Aug 2012 | B2 |
8249601 | Emberson et al. | Aug 2012 | B2 |
8254880 | Aaltonen et al. | Aug 2012 | B2 |
8254915 | Kozisek | Aug 2012 | B2 |
8255515 | Melman et al. | Aug 2012 | B1 |
8255534 | Assadzadeh | Aug 2012 | B2 |
8255689 | Kim et al. | Aug 2012 | B2 |
8259692 | Bajko | Sep 2012 | B2 |
8264965 | Dolganow et al. | Sep 2012 | B2 |
8265004 | Toutonghi | Sep 2012 | B2 |
8266681 | Deshpande et al. | Sep 2012 | B2 |
8270955 | Ramer et al. | Sep 2012 | B2 |
8270972 | Otting et al. | Sep 2012 | B2 |
8271045 | Parolkar et al. | Sep 2012 | B2 |
8271049 | Silver et al. | Sep 2012 | B2 |
8271992 | Chatley et al. | Sep 2012 | B2 |
8275415 | Huslak | Sep 2012 | B2 |
8279067 | Berger et al. | Oct 2012 | B2 |
8279864 | Wood | Oct 2012 | B2 |
8280354 | Smith et al. | Oct 2012 | B2 |
8284740 | O'Connor | Oct 2012 | B2 |
8285249 | Baker et al. | Oct 2012 | B2 |
8291238 | Ginter et al. | Oct 2012 | B2 |
8296404 | McDysan et al. | Oct 2012 | B2 |
8300575 | Willars | Oct 2012 | B2 |
8306518 | Gailloux et al. | Nov 2012 | B1 |
8307067 | Ryan | Nov 2012 | B2 |
8315593 | Gallant et al. | Nov 2012 | B2 |
8315594 | Mauser et al. | Nov 2012 | B1 |
8315718 | Caffrey et al. | Nov 2012 | B2 |
8315999 | Chatley et al. | Nov 2012 | B2 |
8320244 | Muqattash et al. | Nov 2012 | B2 |
8320949 | Matta | Nov 2012 | B2 |
8325638 | Jin et al. | Dec 2012 | B2 |
8326319 | Davis | Dec 2012 | B2 |
8326828 | Zhou et al. | Dec 2012 | B2 |
8331223 | Hill et al. | Dec 2012 | B2 |
8331293 | Sood | Dec 2012 | B2 |
8332375 | Chatley et al. | Dec 2012 | B2 |
8339991 | Biswas et al. | Dec 2012 | B2 |
8340718 | Colonna et al. | Dec 2012 | B2 |
8346210 | Balsan et al. | Jan 2013 | B2 |
8347104 | Pathiyal | Jan 2013 | B2 |
8347362 | Cai et al. | Jan 2013 | B2 |
8347378 | Merkin et al. | Jan 2013 | B2 |
8350700 | Fast et al. | Jan 2013 | B2 |
8351592 | Freeny, Jr. et al. | Jan 2013 | B2 |
8351898 | Raleigh | Jan 2013 | B2 |
8352360 | De Judicibus et al. | Jan 2013 | B2 |
8352980 | Howcroft | Jan 2013 | B2 |
8353001 | Herrod | Jan 2013 | B2 |
8355696 | Olding et al. | Jan 2013 | B1 |
8356336 | Johnston et al. | Jan 2013 | B2 |
8358638 | Scherzer et al. | Jan 2013 | B2 |
8358975 | Bahl et al. | Jan 2013 | B2 |
8363658 | Delker et al. | Jan 2013 | B1 |
8364089 | Phillips | Jan 2013 | B2 |
8364806 | Short et al. | Jan 2013 | B2 |
8369274 | Sawai | Feb 2013 | B2 |
8370477 | Short et al. | Feb 2013 | B2 |
8370483 | Choong et al. | Feb 2013 | B2 |
8374090 | Morrill et al. | Feb 2013 | B2 |
8374592 | Proctor, Jr. et al. | Feb 2013 | B2 |
8375128 | Tofighbakhsh et al. | Feb 2013 | B2 |
8375136 | Roman et al. | Feb 2013 | B2 |
8385896 | Proctor, Jr. et al. | Feb 2013 | B2 |
8385964 | Haney | Feb 2013 | B2 |
8385975 | Forutanpour et al. | Feb 2013 | B2 |
8386386 | Zhu | Feb 2013 | B1 |
8391262 | Maki et al. | Mar 2013 | B2 |
8396458 | Raleigh | Mar 2013 | B2 |
8396929 | Helfman et al. | Mar 2013 | B2 |
8402540 | Kapoor et al. | Mar 2013 | B2 |
8406427 | Chand et al. | Mar 2013 | B2 |
8406736 | Das et al. | Mar 2013 | B2 |
8407763 | Weller et al. | Mar 2013 | B2 |
8411587 | Curtis et al. | Apr 2013 | B2 |
8411691 | Aggarwal | Apr 2013 | B2 |
8422988 | Keshav | Apr 2013 | B1 |
8423016 | Buckley et al. | Apr 2013 | B2 |
8429403 | Moret et al. | Apr 2013 | B2 |
8437734 | Ray et al. | May 2013 | B2 |
8442015 | Behzad et al. | May 2013 | B2 |
8447324 | Shuman et al. | May 2013 | B2 |
8447607 | Weider et al. | May 2013 | B2 |
8447980 | Godfrey et al. | May 2013 | B2 |
8452858 | Wu et al. | May 2013 | B2 |
8461958 | Saenz et al. | Jun 2013 | B2 |
8463232 | Tuli et al. | Jun 2013 | B2 |
8468337 | Gaur et al. | Jun 2013 | B2 |
8472371 | Bari et al. | Jun 2013 | B1 |
8477778 | Lehmann, Jr. et al. | Jul 2013 | B2 |
8483135 | Cai et al. | Jul 2013 | B2 |
8483694 | Lewis et al. | Jul 2013 | B2 |
8484327 | Werner et al. | Jul 2013 | B2 |
8488597 | Nie et al. | Jul 2013 | B2 |
8489110 | Frank et al. | Jul 2013 | B2 |
8489720 | Morford et al. | Jul 2013 | B1 |
8495181 | Venkatraman et al. | Jul 2013 | B2 |
8495227 | Kaminsky et al. | Jul 2013 | B2 |
8495360 | Falk et al. | Jul 2013 | B2 |
8495700 | Shahbazi | Jul 2013 | B2 |
RE44412 | Naqvi et al. | Aug 2013 | E |
8503455 | Heikens | Aug 2013 | B2 |
8504032 | Lott et al. | Aug 2013 | B2 |
8504690 | Shah et al. | Aug 2013 | B2 |
8504729 | Pezzutti | Aug 2013 | B2 |
8509082 | Heinz et al. | Aug 2013 | B2 |
8514927 | Sundararajan et al. | Aug 2013 | B2 |
8516552 | Raleigh | Aug 2013 | B2 |
8520589 | Bhatt et al. | Aug 2013 | B2 |
8521110 | Rofougaran | Aug 2013 | B2 |
8522039 | Hyndman et al. | Aug 2013 | B2 |
8522249 | Beaule | Aug 2013 | B2 |
8522337 | Adusumilli et al. | Aug 2013 | B2 |
8526329 | Mahany et al. | Sep 2013 | B2 |
8526350 | Xue et al. | Sep 2013 | B2 |
8527410 | Markki et al. | Sep 2013 | B2 |
8527662 | Biswas et al. | Sep 2013 | B2 |
8528068 | Weglein et al. | Sep 2013 | B1 |
8532610 | Manning Cassett et al. | Sep 2013 | B2 |
8533775 | Alcorn et al. | Sep 2013 | B2 |
8538394 | Zimmerman et al. | Sep 2013 | B2 |
8538458 | Haney | Sep 2013 | B2 |
8543265 | Ekhaguere et al. | Sep 2013 | B2 |
8544105 | Mclean et al. | Sep 2013 | B2 |
8548427 | Chow et al. | Oct 2013 | B2 |
8554876 | Winsor | Oct 2013 | B2 |
8561138 | Rothman et al. | Oct 2013 | B2 |
8565746 | Hoffman | Oct 2013 | B2 |
8566236 | Busch | Oct 2013 | B2 |
8571474 | Chavez et al. | Oct 2013 | B2 |
8571501 | Miller et al. | Oct 2013 | B2 |
8571598 | Valavi | Oct 2013 | B2 |
8571993 | Kocher et al. | Oct 2013 | B2 |
8572117 | Rappaport | Oct 2013 | B2 |
8572256 | Babbar | Oct 2013 | B2 |
8583499 | De Judicibus et al. | Nov 2013 | B2 |
8589955 | Roundtree et al. | Nov 2013 | B2 |
8601125 | Huang et al. | Dec 2013 | B2 |
8605691 | Soomro et al. | Dec 2013 | B2 |
8631428 | Scott et al. | Jan 2014 | B2 |
8634425 | Gorti et al. | Jan 2014 | B2 |
8635164 | Rosenhaft et al. | Jan 2014 | B2 |
8644702 | Kalajan | Feb 2014 | B1 |
8644813 | Gailloux et al. | Feb 2014 | B1 |
8645518 | David | Feb 2014 | B2 |
8655357 | Gazzard et al. | Feb 2014 | B1 |
8660853 | Robb et al. | Feb 2014 | B2 |
8666395 | Silver | Mar 2014 | B2 |
8667542 | Bertz et al. | Mar 2014 | B1 |
8670334 | Keohane et al. | Mar 2014 | B2 |
8676925 | Liu et al. | Mar 2014 | B1 |
8693323 | McDysan | Apr 2014 | B1 |
8694772 | Kao et al. | Apr 2014 | B2 |
8701015 | Bonnat | Apr 2014 | B2 |
8705361 | Venkataraman et al. | Apr 2014 | B2 |
8706863 | Fadell | Apr 2014 | B2 |
8713535 | Malhotra et al. | Apr 2014 | B2 |
8713641 | Pagan et al. | Apr 2014 | B1 |
8719423 | Wyld | May 2014 | B2 |
8725899 | Short et al. | May 2014 | B2 |
8730842 | Collins et al. | May 2014 | B2 |
8732808 | Sewall et al. | May 2014 | B2 |
8739035 | Trethewey | May 2014 | B2 |
8761711 | Grignani et al. | Jun 2014 | B2 |
8780857 | Balasubramanian et al. | Jul 2014 | B2 |
8793304 | Lu et al. | Jul 2014 | B2 |
8811991 | Jain et al. | Aug 2014 | B2 |
8825109 | Montemurro et al. | Sep 2014 | B2 |
8831561 | Sutaria et al. | Sep 2014 | B2 |
8880047 | Konicek et al. | Nov 2014 | B2 |
8930238 | Coffman et al. | Jan 2015 | B2 |
8948726 | Smith et al. | Feb 2015 | B2 |
8949597 | Reeves et al. | Feb 2015 | B1 |
8966018 | Bugwadia et al. | Feb 2015 | B2 |
8977284 | Reed | Mar 2015 | B2 |
9002342 | Tenhunen et al. | Apr 2015 | B2 |
9014973 | Ruckart | Apr 2015 | B2 |
9049010 | Jueneman et al. | Jun 2015 | B2 |
20010048738 | Baniak et al. | Dec 2001 | A1 |
20010053694 | Igarashi et al. | Dec 2001 | A1 |
20020022472 | Watler et al. | Feb 2002 | A1 |
20020049074 | Eisinger et al. | Apr 2002 | A1 |
20020116338 | Gonthier et al. | Aug 2002 | A1 |
20020120540 | Kende et al. | Aug 2002 | A1 |
20020131404 | Mehta et al. | Sep 2002 | A1 |
20020138601 | Piponius et al. | Sep 2002 | A1 |
20020154751 | Thompson et al. | Oct 2002 | A1 |
20020161601 | Nauer et al. | Oct 2002 | A1 |
20020164983 | Raviv et al. | Nov 2002 | A1 |
20020176377 | Hamilton | Nov 2002 | A1 |
20020188732 | Buckman et al. | Dec 2002 | A1 |
20020191573 | Whitehill et al. | Dec 2002 | A1 |
20020199001 | Wenocur et al. | Dec 2002 | A1 |
20030004937 | Salmenkaita et al. | Jan 2003 | A1 |
20030005112 | Krautkremer | Jan 2003 | A1 |
20030013434 | Rosenberg et al. | Jan 2003 | A1 |
20030018524 | Fishman et al. | Jan 2003 | A1 |
20030046396 | Richter et al. | Mar 2003 | A1 |
20030050070 | Mashinsky et al. | Mar 2003 | A1 |
20030050837 | Kim | Mar 2003 | A1 |
20030084321 | Tarquini et al. | May 2003 | A1 |
20030088671 | Klinker et al. | May 2003 | A1 |
20030133408 | Cheng et al. | Jul 2003 | A1 |
20030159030 | Evans | Aug 2003 | A1 |
20030161265 | Cao et al. | Aug 2003 | A1 |
20030171112 | Lupper et al. | Sep 2003 | A1 |
20030182420 | Jones et al. | Sep 2003 | A1 |
20030182435 | Redlich et al. | Sep 2003 | A1 |
20030188006 | Bard | Oct 2003 | A1 |
20030188117 | Yoshino et al. | Oct 2003 | A1 |
20030220984 | Jones et al. | Nov 2003 | A1 |
20030224781 | Milford et al. | Dec 2003 | A1 |
20030229900 | Reisman | Dec 2003 | A1 |
20030233332 | Keeler et al. | Dec 2003 | A1 |
20030236745 | Hartsell et al. | Dec 2003 | A1 |
20040019539 | Raman et al. | Jan 2004 | A1 |
20040021697 | Beaton et al. | Feb 2004 | A1 |
20040030705 | Bowman-Amuah | Feb 2004 | A1 |
20040039792 | Nakanishi | Feb 2004 | A1 |
20040044623 | Wake et al. | Mar 2004 | A1 |
20040047358 | Chen et al. | Mar 2004 | A1 |
20040073672 | Fascenda | Apr 2004 | A1 |
20040082346 | Skytt et al. | Apr 2004 | A1 |
20040098715 | Aghera et al. | May 2004 | A1 |
20040102182 | Reith et al. | May 2004 | A1 |
20040103193 | Pandya et al. | May 2004 | A1 |
20040107360 | Herrmann et al. | Jun 2004 | A1 |
20040127200 | Shaw et al. | Jul 2004 | A1 |
20040132427 | Lee et al. | Jul 2004 | A1 |
20040133668 | Nicholas, III | Jul 2004 | A1 |
20040137890 | Kalke | Jul 2004 | A1 |
20040168052 | Clisham et al. | Aug 2004 | A1 |
20040170191 | Guo et al. | Sep 2004 | A1 |
20040198331 | Coward et al. | Oct 2004 | A1 |
20040203755 | Brunet et al. | Oct 2004 | A1 |
20040203833 | Rathunde et al. | Oct 2004 | A1 |
20040225898 | Frost et al. | Nov 2004 | A1 |
20040236547 | Rappaport et al. | Nov 2004 | A1 |
20040243992 | Gustafson et al. | Dec 2004 | A1 |
20040249918 | Sunshine | Dec 2004 | A1 |
20040255145 | Chow | Dec 2004 | A1 |
20040259534 | Chaudhari et al. | Dec 2004 | A1 |
20040260766 | Barros et al. | Dec 2004 | A1 |
20050007993 | Chambers et al. | Jan 2005 | A1 |
20050009499 | Koster | Jan 2005 | A1 |
20050021995 | Lal et al. | Jan 2005 | A1 |
20050041617 | Huotari et al. | Feb 2005 | A1 |
20050048950 | Morper | Mar 2005 | A1 |
20050055291 | Bevente et al. | Mar 2005 | A1 |
20050055309 | Williams et al. | Mar 2005 | A1 |
20050055595 | Frazer et al. | Mar 2005 | A1 |
20050060266 | DeMello et al. | Mar 2005 | A1 |
20050075115 | Corneille et al. | Apr 2005 | A1 |
20050079863 | Macaluso | Apr 2005 | A1 |
20050097516 | Donnelly et al. | May 2005 | A1 |
20050107091 | Vannithamby et al. | May 2005 | A1 |
20050128967 | Scobbie | Jun 2005 | A1 |
20050135264 | Popoff et al. | Jun 2005 | A1 |
20050166043 | Zhang et al. | Jul 2005 | A1 |
20050183143 | Anderholm et al. | Aug 2005 | A1 |
20050186948 | Gallagher et al. | Aug 2005 | A1 |
20050198377 | Ferguson et al. | Sep 2005 | A1 |
20050216421 | Barry et al. | Sep 2005 | A1 |
20050228985 | Ylikoski et al. | Oct 2005 | A1 |
20050238046 | Hassan et al. | Oct 2005 | A1 |
20050239447 | Holzman et al. | Oct 2005 | A1 |
20050245241 | Durand et al. | Nov 2005 | A1 |
20050246282 | Naslund et al. | Nov 2005 | A1 |
20050250508 | Guo et al. | Nov 2005 | A1 |
20050250536 | Deng et al. | Nov 2005 | A1 |
20050254435 | Moakley et al. | Nov 2005 | A1 |
20050266825 | Clayton | Dec 2005 | A1 |
20050266880 | Gupta et al. | Dec 2005 | A1 |
20060014519 | Marsh et al. | Jan 2006 | A1 |
20060019632 | Cunningham et al. | Jan 2006 | A1 |
20060026679 | Zakas | Feb 2006 | A1 |
20060030306 | Kuhn | Feb 2006 | A1 |
20060034256 | Addagatla et al. | Feb 2006 | A1 |
20060035631 | White et al. | Feb 2006 | A1 |
20060040642 | Boris et al. | Feb 2006 | A1 |
20060045245 | Aaron et al. | Mar 2006 | A1 |
20060048223 | Lee et al. | Mar 2006 | A1 |
20060068796 | Millen et al. | Mar 2006 | A1 |
20060072451 | Ross | Apr 2006 | A1 |
20060072646 | Feher | Apr 2006 | A1 |
20060075506 | Sanda et al. | Apr 2006 | A1 |
20060085543 | Hrastar et al. | Apr 2006 | A1 |
20060095517 | O'Connor et al. | May 2006 | A1 |
20060098627 | Karaoguz et al. | May 2006 | A1 |
20060112016 | Ishibashi | May 2006 | A1 |
20060114832 | Hamilton et al. | Jun 2006 | A1 |
20060135144 | Jothipragasam | Jun 2006 | A1 |
20060136882 | Noonan et al. | Jun 2006 | A1 |
20060143066 | Calabria | Jun 2006 | A1 |
20060143098 | Lazaridis | Jun 2006 | A1 |
20060156398 | Ross et al. | Jul 2006 | A1 |
20060160536 | Chou | Jul 2006 | A1 |
20060165060 | Dua | Jul 2006 | A1 |
20060168128 | Sistla et al. | Jul 2006 | A1 |
20060173959 | Mckelvie et al. | Aug 2006 | A1 |
20060174035 | Tufail | Aug 2006 | A1 |
20060178917 | Merriam et al. | Aug 2006 | A1 |
20060178918 | Mikurak | Aug 2006 | A1 |
20060183462 | Kolehmainen | Aug 2006 | A1 |
20060190314 | Hernandez | Aug 2006 | A1 |
20060199608 | Dunn et al. | Sep 2006 | A1 |
20060206709 | Labrou et al. | Sep 2006 | A1 |
20060206904 | Watkins et al. | Sep 2006 | A1 |
20060218395 | Maes | Sep 2006 | A1 |
20060233108 | Krishnan | Oct 2006 | A1 |
20060233166 | Bou-Diab et al. | Oct 2006 | A1 |
20060236095 | Smith et al. | Oct 2006 | A1 |
20060242685 | Heard et al. | Oct 2006 | A1 |
20060258341 | Miller et al. | Nov 2006 | A1 |
20060277590 | Limont et al. | Dec 2006 | A1 |
20060291477 | Croak et al. | Dec 2006 | A1 |
20070005795 | Gonzalez | Jan 2007 | A1 |
20070019670 | Falardeau | Jan 2007 | A1 |
20070022289 | Alt et al. | Jan 2007 | A1 |
20070025301 | Petersson et al. | Feb 2007 | A1 |
20070033194 | Srinivas et al. | Feb 2007 | A1 |
20070033197 | Scherzer et al. | Feb 2007 | A1 |
20070036312 | Cai et al. | Feb 2007 | A1 |
20070055694 | Ruge et al. | Mar 2007 | A1 |
20070060200 | Boris et al. | Mar 2007 | A1 |
20070061243 | Ramer et al. | Mar 2007 | A1 |
20070061878 | Hagiu et al. | Mar 2007 | A1 |
20070073899 | Judge et al. | Mar 2007 | A1 |
20070076616 | Ngo et al. | Apr 2007 | A1 |
20070093243 | Kapadekar et al. | Apr 2007 | A1 |
20070100981 | Adamczyk et al. | May 2007 | A1 |
20070101426 | Lee et al. | May 2007 | A1 |
20070104126 | Calhoun et al. | May 2007 | A1 |
20070109983 | Shankar et al. | May 2007 | A1 |
20070130315 | Friend et al. | Jun 2007 | A1 |
20070140113 | Gemelos | Jun 2007 | A1 |
20070140145 | Kumar et al. | Jun 2007 | A1 |
20070140275 | Bowman et al. | Jun 2007 | A1 |
20070143824 | Shahbazi | Jun 2007 | A1 |
20070147317 | Smith et al. | Jun 2007 | A1 |
20070147324 | McGary | Jun 2007 | A1 |
20070155365 | Kim et al. | Jul 2007 | A1 |
20070165630 | Rasanen et al. | Jul 2007 | A1 |
20070168499 | Chu | Jul 2007 | A1 |
20070174490 | Choi et al. | Jul 2007 | A1 |
20070192460 | Choi et al. | Aug 2007 | A1 |
20070198656 | Mazzaferri et al. | Aug 2007 | A1 |
20070213054 | Han | Sep 2007 | A1 |
20070220251 | Rosenberg et al. | Sep 2007 | A1 |
20070226225 | Yiu et al. | Sep 2007 | A1 |
20070226775 | Andreasen et al. | Sep 2007 | A1 |
20070234402 | Khosravi et al. | Oct 2007 | A1 |
20070243862 | Coskun et al. | Oct 2007 | A1 |
20070248100 | Zuberi et al. | Oct 2007 | A1 |
20070254675 | Zorlu Ozer et al. | Nov 2007 | A1 |
20070255848 | Sewall et al. | Nov 2007 | A1 |
20070257767 | Beeson | Nov 2007 | A1 |
20070259656 | Jeong | Nov 2007 | A1 |
20070259673 | Willars et al. | Nov 2007 | A1 |
20070263558 | Salomone | Nov 2007 | A1 |
20070266422 | Germano et al. | Nov 2007 | A1 |
20070274327 | Kaarela et al. | Nov 2007 | A1 |
20070280453 | Kelley et al. | Dec 2007 | A1 |
20070282896 | Wydroug et al. | Dec 2007 | A1 |
20070293191 | Mir et al. | Dec 2007 | A1 |
20070294395 | Strub et al. | Dec 2007 | A1 |
20070294410 | Pandya et al. | Dec 2007 | A1 |
20070298764 | Clayton | Dec 2007 | A1 |
20070300252 | Acharya et al. | Dec 2007 | A1 |
20080005285 | Robinson et al. | Jan 2008 | A1 |
20080005561 | Brown et al. | Jan 2008 | A1 |
20080010379 | Zhao | Jan 2008 | A1 |
20080010452 | Holtzman et al. | Jan 2008 | A1 |
20080018494 | Waite et al. | Jan 2008 | A1 |
20080022354 | Grewal et al. | Jan 2008 | A1 |
20080025230 | Patel et al. | Jan 2008 | A1 |
20080032715 | Jia et al. | Feb 2008 | A1 |
20080034063 | Yee | Feb 2008 | A1 |
20080034419 | Mullick et al. | Feb 2008 | A1 |
20080039102 | Sewall et al. | Feb 2008 | A1 |
20080049630 | Kozisek et al. | Feb 2008 | A1 |
20080050715 | Golczewski et al. | Feb 2008 | A1 |
20080051076 | O'Shaughnessy et al. | Feb 2008 | A1 |
20080052387 | Heinz et al. | Feb 2008 | A1 |
20080056273 | Pelletier et al. | Mar 2008 | A1 |
20080059474 | Lim | Mar 2008 | A1 |
20080059743 | Bychkov et al. | Mar 2008 | A1 |
20080060066 | Wynn et al. | Mar 2008 | A1 |
20080062900 | Rao | Mar 2008 | A1 |
20080064367 | Nath et al. | Mar 2008 | A1 |
20080066149 | Lim | Mar 2008 | A1 |
20080066150 | Lim | Mar 2008 | A1 |
20080070550 | Hose | Mar 2008 | A1 |
20080080457 | Cole | Apr 2008 | A1 |
20080081606 | Cole | Apr 2008 | A1 |
20080082643 | Storrie et al. | Apr 2008 | A1 |
20080083013 | Soliman et al. | Apr 2008 | A1 |
20080085707 | Fadell | Apr 2008 | A1 |
20080089295 | Keeler et al. | Apr 2008 | A1 |
20080095339 | Elliott et al. | Apr 2008 | A1 |
20080098062 | Balia | Apr 2008 | A1 |
20080109679 | Wright et al. | May 2008 | A1 |
20080120129 | Seubert et al. | May 2008 | A1 |
20080120668 | Yau | May 2008 | A1 |
20080120688 | Qiu et al. | May 2008 | A1 |
20080125079 | O'Neil et al. | May 2008 | A1 |
20080127304 | Ginter et al. | May 2008 | A1 |
20080130534 | Tomioka | Jun 2008 | A1 |
20080130656 | Kim et al. | Jun 2008 | A1 |
20080132201 | Karlberg | Jun 2008 | A1 |
20080132268 | Choi-Grogan et al. | Jun 2008 | A1 |
20080134330 | Kapoor et al. | Jun 2008 | A1 |
20080139210 | Gisby et al. | Jun 2008 | A1 |
20080147454 | Walker et al. | Jun 2008 | A1 |
20080160958 | Abichandani et al. | Jul 2008 | A1 |
20080162637 | Adamczyk et al. | Jul 2008 | A1 |
20080162704 | Poplett et al. | Jul 2008 | A1 |
20080164304 | Narasimhan et al. | Jul 2008 | A1 |
20080166993 | Gautier et al. | Jul 2008 | A1 |
20080167027 | Gautier et al. | Jul 2008 | A1 |
20080167033 | Beckers | Jul 2008 | A1 |
20080168523 | Ansari et al. | Jul 2008 | A1 |
20080177998 | Apsangi et al. | Jul 2008 | A1 |
20080183812 | Paul et al. | Jul 2008 | A1 |
20080184127 | Rafey et al. | Jul 2008 | A1 |
20080189760 | Rosenberg et al. | Aug 2008 | A1 |
20080201266 | Chua et al. | Aug 2008 | A1 |
20080207167 | Bugenhagen | Aug 2008 | A1 |
20080212470 | Castaneda et al. | Sep 2008 | A1 |
20080219268 | Dennison | Sep 2008 | A1 |
20080221951 | Stanforth et al. | Sep 2008 | A1 |
20080222692 | Andersson et al. | Sep 2008 | A1 |
20080225748 | Khemani et al. | Sep 2008 | A1 |
20080229385 | Feder et al. | Sep 2008 | A1 |
20080229388 | Maes | Sep 2008 | A1 |
20080235511 | O'Brien et al. | Sep 2008 | A1 |
20080240373 | Wilhelm | Oct 2008 | A1 |
20080250053 | Aaltonen et al. | Oct 2008 | A1 |
20080256593 | Vinberg et al. | Oct 2008 | A1 |
20080262798 | Kim et al. | Oct 2008 | A1 |
20080263348 | Zaltsman et al. | Oct 2008 | A1 |
20080268813 | Maes | Oct 2008 | A1 |
20080270212 | Blight et al. | Oct 2008 | A1 |
20080282319 | Fontijn et al. | Nov 2008 | A1 |
20080293395 | Mathews et al. | Nov 2008 | A1 |
20080298230 | Luft et al. | Dec 2008 | A1 |
20080305793 | Gallagher et al. | Dec 2008 | A1 |
20080311885 | Dawson et al. | Dec 2008 | A1 |
20080313315 | Karaoguz et al. | Dec 2008 | A1 |
20080313730 | Iftimie et al. | Dec 2008 | A1 |
20080316923 | Fedders et al. | Dec 2008 | A1 |
20080318547 | Ballou et al. | Dec 2008 | A1 |
20080318550 | DeAtley | Dec 2008 | A1 |
20080319879 | Carroll et al. | Dec 2008 | A1 |
20090005000 | Baker et al. | Jan 2009 | A1 |
20090005005 | Forstall et al. | Jan 2009 | A1 |
20090006116 | Baker et al. | Jan 2009 | A1 |
20090006200 | Baker et al. | Jan 2009 | A1 |
20090013157 | Beaule | Jan 2009 | A1 |
20090036111 | Danford et al. | Feb 2009 | A1 |
20090044185 | Krivopaltsev | Feb 2009 | A1 |
20090046707 | Smires et al. | Feb 2009 | A1 |
20090046723 | Rahman et al. | Feb 2009 | A1 |
20090048913 | Shenfield et al. | Feb 2009 | A1 |
20090049518 | Roman et al. | Feb 2009 | A1 |
20090054030 | Golds | Feb 2009 | A1 |
20090067372 | Shah et al. | Mar 2009 | A1 |
20090068984 | Burnett | Mar 2009 | A1 |
20090070379 | Rappaport | Mar 2009 | A1 |
20090077622 | Baum et al. | Mar 2009 | A1 |
20090079699 | Sun | Mar 2009 | A1 |
20090113514 | Hu | Apr 2009 | A1 |
20090125619 | Antani | May 2009 | A1 |
20090157792 | Fiatal | Jun 2009 | A1 |
20090163173 | Williams | Jun 2009 | A1 |
20090172077 | Roxburgh et al. | Jul 2009 | A1 |
20090180391 | Petersen et al. | Jul 2009 | A1 |
20090181662 | Fleischman et al. | Jul 2009 | A1 |
20090197585 | Aaron | Aug 2009 | A1 |
20090197612 | Kiiskinen | Aug 2009 | A1 |
20090219170 | Clark et al. | Sep 2009 | A1 |
20090248883 | Suryanarayana et al. | Oct 2009 | A1 |
20090254857 | Romine et al. | Oct 2009 | A1 |
20090257379 | Robinson et al. | Oct 2009 | A1 |
20090271514 | Thomas et al. | Oct 2009 | A1 |
20090282127 | Leblanc et al. | Nov 2009 | A1 |
20090286507 | O'Neil et al. | Nov 2009 | A1 |
20090287921 | Zhu et al. | Nov 2009 | A1 |
20090288140 | Huber et al. | Nov 2009 | A1 |
20090299857 | Brubaker | Dec 2009 | A1 |
20090307746 | Di et al. | Dec 2009 | A1 |
20090315735 | Bhavani et al. | Dec 2009 | A1 |
20100017506 | Fadell | Jan 2010 | A1 |
20100020822 | Zerillo et al. | Jan 2010 | A1 |
20100027469 | Gurajala et al. | Feb 2010 | A1 |
20100027559 | Lin et al. | Feb 2010 | A1 |
20100030890 | Dutta et al. | Feb 2010 | A1 |
20100041364 | Lott et al. | Feb 2010 | A1 |
20100042675 | Fujii | Feb 2010 | A1 |
20100043068 | Varadhan et al. | Feb 2010 | A1 |
20100071053 | Ansari et al. | Mar 2010 | A1 |
20100075666 | Garner | Mar 2010 | A1 |
20100080202 | Hanson | Apr 2010 | A1 |
20100082431 | Ramer et al. | Apr 2010 | A1 |
20100103820 | Fuller et al. | Apr 2010 | A1 |
20100131584 | Johnson | May 2010 | A1 |
20100144310 | Bedingfield | Jun 2010 | A1 |
20100151866 | Karpov et al. | Jun 2010 | A1 |
20100153781 | Hanna | Jun 2010 | A1 |
20100167696 | Smith et al. | Jul 2010 | A1 |
20100188975 | Raleigh | Jul 2010 | A1 |
20100188990 | Raleigh | Jul 2010 | A1 |
20100188992 | Raleigh | Jul 2010 | A1 |
20100188994 | Raleigh | Jul 2010 | A1 |
20100191576 | Raleigh | Jul 2010 | A1 |
20100191612 | Raleigh | Jul 2010 | A1 |
20100191846 | Raleigh | Jul 2010 | A1 |
20100192170 | Raleigh | Jul 2010 | A1 |
20100192212 | Raleigh | Jul 2010 | A1 |
20100195503 | Raleigh | Aug 2010 | A1 |
20100197268 | Raleigh | Aug 2010 | A1 |
20100198698 | Raleigh et al. | Aug 2010 | A1 |
20100198939 | Raleigh | Aug 2010 | A1 |
20100235329 | Koren et al. | Sep 2010 | A1 |
20100241544 | Benson et al. | Sep 2010 | A1 |
20100248719 | Scholaert | Sep 2010 | A1 |
20100284327 | Miklos | Nov 2010 | A1 |
20100287599 | He et al. | Nov 2010 | A1 |
20100311402 | Srinivasan et al. | Dec 2010 | A1 |
20100325420 | Kanekar | Dec 2010 | A1 |
20110013569 | Scherzer et al. | Jan 2011 | A1 |
20110019574 | Malomsoky et al. | Jan 2011 | A1 |
20110081881 | Baker et al. | Apr 2011 | A1 |
20110082790 | Baker et al. | Apr 2011 | A1 |
20110110309 | Bennett | May 2011 | A1 |
20110126141 | King et al. | May 2011 | A1 |
20110145920 | Mahaffey et al. | Jun 2011 | A1 |
20110159818 | Scherzer et al. | Jun 2011 | A1 |
20110173678 | Kaippallimalil et al. | Jul 2011 | A1 |
20110264923 | Kocher et al. | Oct 2011 | A1 |
20110277019 | Pritchard, Jr. | Nov 2011 | A1 |
20120020296 | Scherzer et al. | Jan 2012 | A1 |
20120196644 | Scherzer et al. | Aug 2012 | A1 |
20120238287 | Scherzer | Sep 2012 | A1 |
20130029653 | Baker et al. | Jan 2013 | A1 |
20130058274 | Scherzer et al. | Mar 2013 | A1 |
20130065555 | Baker et al. | Mar 2013 | A1 |
20130084835 | Scherzer et al. | Apr 2013 | A1 |
20130144789 | Aaltonen et al. | Jun 2013 | A1 |
20130326356 | Zheng et al. | Dec 2013 | A9 |
Number | Date | Country |
---|---|---|
2688553 | Dec 2008 | CA |
1310401 | Aug 2001 | CN |
1508734 | Jun 2004 | CN |
1538730 | Oct 2004 | CN |
1567818 | Jan 2005 | CN |
101035308 | Mar 2006 | CN |
1801829 | Jul 2006 | CN |
1802839 | Jul 2006 | CN |
1889777 | Jul 2006 | CN |
101155343 | Sep 2006 | CN |
1867024 | Nov 2006 | CN |
1878160 | Dec 2006 | CN |
1937511 | Mar 2007 | CN |
101123553 | Sep 2007 | CN |
101080055 | Nov 2007 | CN |
101115248 | Jan 2008 | CN |
101127988 | Feb 2008 | CN |
101183958 | May 2008 | CN |
101335666 | Dec 2008 | CN |
101341764 | Jan 2009 | CN |
101815275 | Aug 2010 | CN |
1463238 | Sep 2004 | EP |
1503548 | Feb 2005 | EP |
1739518 | Jan 2007 | EP |
1772988 | Apr 2007 | EP |
1850575 | Oct 2007 | EP |
1978772 | Oct 2008 | EP |
3148713 | Mar 2001 | JP |
2007318354 | Dec 2007 | JP |
2008301121 | Dec 2008 | JP |
2009111919 | May 2009 | JP |
2009212707 | Sep 2009 | JP |
2009218773 | Sep 2009 | JP |
2009232107 | Oct 2009 | JP |
9858505 | Dec 1998 | WO |
9927723 | Jun 1999 | WO |
9965185 | Dec 1999 | WO |
03014891 | Feb 2003 | WO |
03058880 | Jul 2003 | WO |
2004028070 | Apr 2004 | WO |
2004064306 | Jul 2004 | WO |
2004077797 | Sep 2004 | WO |
2004095753 | Nov 2004 | WO |
2005008995 | Jan 2005 | WO |
2006004467 | Jan 2006 | WO |
2006012610 | Feb 2006 | WO |
2006050758 | May 2006 | WO |
2006073837 | Jul 2006 | WO |
2006077481 | Jul 2006 | WO |
2006093961 | Sep 2006 | WO |
2006120558 | Nov 2006 | WO |
2006130960 | Dec 2006 | WO |
2007001833 | Jan 2007 | WO |
2007014630 | Feb 2007 | WO |
2007018363 | Feb 2007 | WO |
2007053848 | May 2007 | WO |
2007068288 | Jun 2007 | WO |
2007069245 | Jun 2007 | WO |
2007097786 | Aug 2007 | WO |
2007107701 | Sep 2007 | WO |
2007124279 | Nov 2007 | WO |
2007126352 | Nov 2007 | WO |
2007133844 | Nov 2007 | WO |
2008017837 | Feb 2008 | WO |
2008051379 | May 2008 | WO |
2008066419 | Jun 2008 | WO |
2008080139 | Jul 2008 | WO |
2008080430 | Jul 2008 | WO |
2008099802 | Aug 2008 | WO |
2010088413 | Aug 2010 | WO |
Entry |
---|
First Examination Report in Australian Application No. 2010208314 dated Aug. 27, 2014. |
3rd Generation Partnership Project, “Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) Enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Access,” Release 8, Document No. 3GPP TS 23.401, V8.4.0, Dec. 2008. |
3rd Generation Partnership Project, “Technical Specification Group Services and System Aspects; Policy and Charging Control Architecture,” Release 8, Document No. 3GPP TS 23.203, V8.4.0, Dec. 2008. |
Alonistioti et al., “Intelligent Architectures Enabling Flexible Service Provision and Adaptability,” 2002. |
Amazon Technologies, Inc., “Kindle™ User's Guide,” 3rd Edition, Copyright 2004-2009. |
Chandrasekhar et al., “Femtocell Networks: A Survey,” Jun. 28, 2008. |
Chaouchi et al., “Policy Based Networking in the Integration Effort of 4G Networks and Services,” 2004 IEEE. |
Cisco Systems, Inc., “Cisco Mobile Exchange (CMX) Solution Guide: Chapter 2—Overview of GSM, GPRS, and UMTS,” Nov. 4, 2008. |
Dikaiakos et al., “A Distributed Middleware Infrastructure for Personalized Services,” Nov. 24, 2003. |
European Commission, “Data Roaming Tariffs—Transparency Measures,” [online] retrieved from http://web.archive.org/web/20081220232754/http://ec.europa.eu/information—society/activities/roaming/data/measures/index—en.htm, Dec. 20, 2008 [retrieved May 16, 2012]. |
Farooq et al., “An IEEE 802.16 WiMax Module for the NS-3 Simulator,” Mar. 2-6, 2009. |
Han et al., “Information Collection Services for Qos-Aware Mobile Applications,” 2005. |
Hartmann et al., “Agent-Based Banking Transactions & Information Retrieval—What About Performance Issues?” 1999. |
Hewlett-Packard Development Company, LP, “IP Multimedia Services Charging,” white paper, Jan. 2006. |
Hossain et al., “Gain-Based Selection of Ambient Media Services in Pervasive Environments,” Mobile Networks and Applications. Oct. 3, 2008. |
Knight et al., “Layer 2 and 3 Virtual Private Networks: Taxonomy, Technology, and Standarization Efforts,” IEEE Communications Magazine, Jun. 2004. |
Koutsopoulou et al., “Middleware Platform for the Support of Charging Reconfiguration Actions,” 2005. |
Kyriakakos et al., “Ubiquitous Service Provision in Next Generation Mobile Networks,” Proceedings of the 13th IST Mobile and Wireless Communications Summit, Lyon, France, Jun. 2004. |
Li, Yu, “Dedicated E-Reading Device: The State of the Art and the Challenges,” Scroll, vol. 1, No. 1, 2008. |
Nilsson et al., “A Novel MAC Scheme for Solving the QoS Parameter Adjustment Problem in IEEE802.11e EDCA,” Feb. 2006. |
Oppliger, Rolf, “Internet Security: Firewalls and Bey,” Communications of the ACM, May 1997, vol. 40. No. 5. |
Rao et al., “Evolution of Mobile Location-Based Services,” Communication of the ACM, Dec. 2003. |
Steglich, Stephan, “I-Centric User Interaction,” Nov. 21, 2003. |
Van Eijk, et al., “GigaMobile, Agent Technology for Designing Personalized Mobile Service Brokerage,” Jul. 1, 2002. |
Zhu et al., “A Survey of Quality of Service in IEEE 802.11 Networks,” IEEE Wireless Communications, Aug. 2004. |
Accuris Networks, “The Business Value of Mobile Data Offload—a White Paper”, 2010. |
Anton, B. et al., “Best Current Practices for Wireless Internet Service Provider (WISP) Roaming”; Release Date Feb. 2003, Version 1.0; Wi-Fi Alliance—Wireless ISP Roaming (WISPr). |
Ruckus Wireless—White Paper; “Smarter Wi-Fi for Mobile Operator Infrastructures” 2010. |
Wireless Broadband Alliance, “WISPr 2.0, Apr. 8, 2010”; Doc. Ref. No. WBA/RM/WISPr, Version 01.00. |
“End to End QoS Solution for Real-time Multimedia Application;” Computer Engineering and Applications, 2007, 43 (4):155-159, by Tan Zu-guo, Wang Wen-juan; Information and Science School, Zhanjian Normal College, Zhan jiang, Guangdong 524048, China. |
“ASA/PIX: Allow Split Tunneling for VPN Clients on the ASA Configuration Example,” Document ID 70917, Jan. 10, 2008. |
Apr. 14, 2014 European Search Report and Opinion in European Application No. 10736355.8. |
“The Construction of Intelligent Residential District in Use of Cable Television Network,” Shandong Science, vol. 13, No. 2, Jun. 2000. |
VerizonWireless.com news, “Verizon Wireless Adds to Portfolio of Cosumer-Friendly Tools With Introduction of Usage Controls, Usage Controls and Chaperone 2.0 Offer Parents Full Family Security Solution,” Aug. 18, 2008. |
Oct. 25, 2013 Office Action in Chinese Patent Application No. 201080010929.2. |
Second Office Action in Chinese Patent Application No. 201080010929.2, dated Aug. 22, 2014. |
Nov. 12, 2014 Response to European Search Report and Opinion in European Application No. 10736355.8. |
“Communication Concepts for Mobile Agent Systems,” by Joachim Baumann et al.; Inst. of Parallel and Distributed High-Performance Systems, Univ. of Stuttgart, Germany, pp. 123-135, 1997. |
Oct. 25, 2013 First Office Action in Chinese Patent Application No. 201080010929.2. |
Ahmed et al., “A Context-Aware Vertical Handover Decision Algorithm for Multimode Mobile Terminals and Its Performance,” BenQ Mobile, Munich Germany; University of Klagenfurt, Klagenfurt, Austria; 2006. |
Dixon et al., Triple Play Digital Services: Comcast and Verizon (Digital Phone, Television, and Internet), Aug. 2007. |
Kassar et al., “An overview of vertical handover decision strategies in heterogeneous wireless networks,” ScienceDirect, University Pierre & Marie Curie, Paris, France, Jun. 5, 2007. |
Sadeh et al., “Understanding and Capturing People's Privacy Policies in a Mobile Social Networking Application,” ISR School of Computer Science, Carnegie Mellon University, 2007. |
Schiller et al., “Location-Based Services,” The Morgan Kaufmann Series in Data Management Systems, 2004. |
“Ads and movies on the run,” The Gold Coast Bulletin, Southport, Qld, Jan. 29, 2008. |
“Jentro Technologies launches Zenlet platform to accelerate location-based content delivery to mobile devices,” The Mobile Internet, Boston, MA, Feb. 2008. |
Jing et al., “Client-Server Computing in Mobile Environments,” GTE Labs. Inc., Purdue University, ACM Computing Surveys, vol. 31, No. 2, Jun. 1999. |
Kim, “Free wireless a high-wire act; MetroFi needs to draw enough ads to make service add profits,” San Francisco Chronicle, Aug. 21, 2006. |
Koutsopoulou et al., “Charging, Accounting and Billing Management Schemes in Mobile Telecommunication Networks and the Internet,” IEEE Communications Surveys & Tutorials, First Quarter 2004, vol. 6, No. 1. |
Loopt User Guide, metroPCS, Jul. 17, 2008. |
Nuzman et al., “A compund model for TCP connection arrivals for LAN and WAN applications,” Oct. 22, 2002. |
Richtel, “Cellphone consumerism; If even a debit card is too slow, now you have a new way to act on impulse: [National Edition],” National Post, Canada, Oct. 2, 2007. |
Rivadeneyra et al., “A communication architecture to access data services through GSM,” San Sebastian, Spain, 1998. |
Sabat, “The evolving mobile wireless value chain and market structure,” Nov. 2002. |
Sun et al., “Towards Connectivity Management Adaptability: Context Awareness in Policy Representation and End-to-end Evaluation Algorithm,” Dept. of Electrical and Information Engineering, Univ. of Oulu, Finland, 2004. |
Number | Date | Country | |
---|---|---|---|
20130107706 A1 | May 2013 | US |
Number | Date | Country | |
---|---|---|---|
61206354 | Jan 2009 | US | |
61206944 | Feb 2009 | US | |
61207393 | Feb 2009 | US | |
61207739 | Feb 2009 | US | |
61252151 | Oct 2009 | US | |
61252153 | Oct 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12695021 | Jan 2010 | US |
Child | 13718917 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12380780 | Mar 2009 | US |
Child | 12695021 | US |