US7039037B2 - Method and apparatus for providing service selection, redirection and managing of subscriber access to multiple WAP (Wireless Application Protocol) gateways simultaneously - Google Patents

Method and apparatus for providing service selection, redirection and managing of subscriber access to multiple WAP (Wireless Application Protocol) gateways simultaneously Download PDF

Info

Publication number
US7039037B2
US7039037B2 US09/933,781 US93378101A US7039037B2 US 7039037 B2 US7039037 B2 US 7039037B2 US 93378101 A US93378101 A US 93378101A US 7039037 B2 US7039037 B2 US 7039037B2
Authority
US
United States
Prior art keywords
wireless
wap
service
routing
gateway
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US09/933,781
Other versions
US20030035409A1 (en
Inventor
Jiwei R. Wang
Alin Jayant
Vincent Kadar
Ken Kim
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Mavenir Systems Inc
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US09/933,781 priority Critical patent/US7039037B2/en
Assigned to TARAL NETWORKS, INC. reassignment TARAL NETWORKS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: JAYANT, ALIN, KADAR, VINCENT, KIM, KEN, WANG, JIWEI R.
Publication of US20030035409A1 publication Critical patent/US20030035409A1/en
Assigned to PARTNERS FOR GROWTH, L.P. reassignment PARTNERS FOR GROWTH, L.P. SECURITY AGREEMENT Assignors: AIRWIDE SOLUTIONS INC.
Assigned to SILICON VALLEY BANK reassignment SILICON VALLEY BANK SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: AIRWIDE SOLUTIONS INC.
Application granted granted Critical
Publication of US7039037B2 publication Critical patent/US7039037B2/en
Assigned to AIRWIDE SOLUTIONS INC. reassignment AIRWIDE SOLUTIONS INC. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: SILICON VALLEY BANK
Assigned to AIRWIDE SOLUTIONS UK LTD., AIRWIDE SOLUTIONS HOLDINGS LTD., AIRWIDE SOLUTIONS INC., AIRWIDE SOLUTIONS NORTH AMERICA LTD. reassignment AIRWIDE SOLUTIONS UK LTD. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: PARTNERS FOR GROWTH, L.P.
Assigned to LIGHTHOUSE CAPITAL PARTNERS VI, L.P. reassignment LIGHTHOUSE CAPITAL PARTNERS VI, L.P. SECURITY AGREEMENT Assignors: AIRWIDE SOLUTIONS INC.
Assigned to LIGHTHOUSE CAPITAL PARTNERS VI, L.P. reassignment LIGHTHOUSE CAPITAL PARTNERS VI, L.P. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: AIRWIDE SOLUTIONS INC.
Assigned to AIRWIDE SOLUTIONS INC. reassignment AIRWIDE SOLUTIONS INC. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: LIGHTHOUSE CAPITAL PARTNERS VI, L.P.
Assigned to COMERICA BANK reassignment COMERICA BANK SECURITY AGREEMENT Assignors: MAVENIR HOLDINGS, INC. FORMERLY KNOWN AS AIRWIDE SOLUTIONS INC.
Assigned to SILICON VALLEY BANK reassignment SILICON VALLEY BANK SECURITY AGREEMENT Assignors: MAVENIR HOLDINGS, INC., MAVENIR SYSTEMS, INC.
Assigned to MAVENIR HOLDINGS, INC., FORMERLY KNOWN AS AIRWIDE SOLUTIONS, INC. reassignment MAVENIR HOLDINGS, INC., FORMERLY KNOWN AS AIRWIDE SOLUTIONS, INC. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: COMERICA BANK, A TEXAS BANKING ASSOCIATION
Assigned to MAVENIR HOLDINGS, INC. reassignment MAVENIR HOLDINGS, INC. MERGER (SEE DOCUMENT FOR DETAILS). Assignors: AIRWIDE SOLUTIONS INC.
Assigned to MAVENIR INTERNATIONAL HOLDINGS, INC. FKA STOKE, INC., MAVENIR SYSTEMS, INC., MAVENIR HOLDINGS, INC., MAVENIR SYSTEMS IP HOLDINGS, LLC reassignment MAVENIR INTERNATIONAL HOLDINGS, INC. FKA STOKE, INC. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: SILICON VALLEY BANK
Assigned to AIRWIDE SOLUTIONS INC. reassignment AIRWIDE SOLUTIONS INC. CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: TARAL NETWORKS, INC.
Assigned to MITEL MOBILITY, INC. reassignment MITEL MOBILITY, INC. MERGER AND CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: MAVENIR HOLDINGS, INC., MITEL MOBILITY, INC.
Assigned to CERBERUS BUSINESS FINANCE, LLC, AS COLLATERAL AGENT reassignment CERBERUS BUSINESS FINANCE, LLC, AS COLLATERAL AGENT GRANT OF A SECURITY INTEREST -- PATENTS Assignors: MAVENIR SYSTEMS, INC. (F/K/A MITEL MOBILITY INC.)
Assigned to MAVENIR SYSTEMS, INC. reassignment MAVENIR SYSTEMS, INC. CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: MITEL MOBILITY INC.
Assigned to MAVENIR SYSTEMS, INC. (F/K/A MITEL MOBILITY INC.) reassignment MAVENIR SYSTEMS, INC. (F/K/A MITEL MOBILITY INC.) RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: CERBERUS BUSINESS FINANCE, LLC, AS COLLATERAL AGENT
Assigned to GOLDMAN SACHS LENDING PARTNERS LLC, AS COLLATERAL AGENT reassignment GOLDMAN SACHS LENDING PARTNERS LLC, AS COLLATERAL AGENT GRANT OF SECURITY INTEREST IN PATENTS Assignors: MAVENIR SYSTEMS, INC.
Assigned to JPMORGAN CHASE BANK, N.A. reassignment JPMORGAN CHASE BANK, N.A. SECURITY AGREEMENT Assignors: MAVENIR SYSTEMS, INC.
Assigned to MAVENIR SYSTEMS, INC. reassignment MAVENIR SYSTEMS, INC. TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL - RELEASE OF 046139.0299 Assignors: GOLDMAN SACHS LENDING PARTNERS LLC, AS COLLATERAL AGENT
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/20Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/09Mapping addresses
    • H04L61/10Mapping addresses of different types
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/04Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/2866Architectures; Arrangements
    • H04L67/30Profiles
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/564Enhancement of application control based on intercepted application data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/164Adaptation or special uses of UDP protocol
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02Terminal devices

Definitions

  • the embodiments disclosed herein relate to the development and use of a smart controller to provide dynamic service selection, policing, redirection and management of WAP (Wireless Application Protocol) traffic, or like wireless data traffic, in a wireless data network.
  • WAP Wireless Application Protocol
  • the embodiments relates to:
  • WAP Wireless Application Protocol
  • WAP Forum http://www.wapforum.org
  • Ref-1, Ref-5 a standard proposed by the WAP Forum (http://www.wapforum.org) [Ref-1, Ref-5] that allows information to be sent and received by wireless devices.
  • WAP has been deployed in several existing cellular wireless data networks (e.g., GSM, TDMA and CDMA).
  • WAP capable wireless devices have several operational constraints compared to traditional Internet access devices such as personal computers. These limitations include a less powerful CPU, less memory, restricted power consumption, smaller display, and different input methods to the device. In addition, WAP devices operate in an environment that generally provides less bandwidth, less connection stability, less predictable availability, and greater latency than their wire-line counterparts. With these considerations, the WAP Forum introduced a new network element called the WAP Gateway that was targeted at addressing one or more of these issues.
  • the WAP gateway splits this process acting as a proxy (i.e. hosting default home page, recording cookies, content and protocol conversions, etc.) for the devices as shown in FIG. 1A .
  • the WAP gateway has been forced to provide several adjacent functions that assist in the end-to-end flow of data as part of the bridging or proxy function that they perform in the wireless network.
  • Another prior art concept is the unique identification of subscriber in the IP and wireless domains.
  • the WAP standard does not allow the device to send in a unique identifier in its requests, where one such identifier may be the phone number of the device, commonly referred as the MSISDN (Mobile Subscriber ISDN number).
  • MSISDN Mobile Subscriber ISDN number
  • This inability to transmit an ID poses a serious challenge to the application development on the Web server which does not have a consistent means to identify the WAP device and hence the user.
  • the solution, from application development side is to require the user to log on by typing a user ID or MSISDN plus a password. Owing to the limited capability of the input method on the device, this is both inconvenient and difficult.
  • WAP gateway vendors have developed solutions to obtain IP address to MSISDN mapping from the NAS (Network Access Server) or AAA (Authentication, Authorization and Accounting) server.
  • the WAP gateway then can identify each WAP request by the IP address and pass the MSISDN either in the URL or the HTTP header to applications running on Web servers.
  • This requires the WAP gateway to collocate with the NAS or AAA in the carrier domain, which limits the configuration possibilities of the system.
  • Enterprises and Wireless Portals who would like to control user experience by owning the WAP gateway will not have access to this critical information in the NAS or AAA, whereby flexibility within the system is lost when using this approach.
  • the subscriber is presented multiple origin server choices through a single WAP gateway (WAP implementations/protocol associate a WAP device with a single WAP gateway).
  • the IP address of the WAP gateway is embedded in the WAP device restricting the device from accessing any other end-point directly and forcing one single WAP gateway to provide all services to the WAP device. This severely restricts the flexibility and scope of services that may be provided to the end user. In summary, this type of a system results in two major problems:
  • a data request is encrypted by the WAP device and transmitted over the WAP device to the WAP gateway using the Wireless Transport Layer Security (WTLS) protocol [Ref-6].
  • WTLS Wireless Transport Layer Security
  • the WAP gateway is then forced to decrypt the message and then re-encrypt it using another protocol (e.g. Secure Socket Layer) before transmitting it to the data content site origin server ( FIG. 1B ).
  • the WTLS certificate only authenticates the WAP device to the WAP gateway. Therefore, to ensure end-to-end authentication, the WAP gateway would need to reside on the content site.
  • the presence of an embedded WAP gateway IP address in the WAP device forces the subscriber to break connection with the network, re-program the IP address in the WAP device for each separate WAP service access.
  • a conventional multiple-profile system the subscriber defines multiple profiles with each profile containing a unique WAP gateway IP address, NAS (Network Access Server) dialup number, user ID and password.
  • NAS Network Access Server
  • switching to a new application forces the subscriber to terminate the current session, modify the profile choice, and start a new session.
  • Dynamically changing the WAP gateway provider within the same session is impossible using conventional techniques and systems.
  • the process to create multiple profiles is cumbersome, tedious, and technically challenging.
  • wireless network operators have no control over a user's selection on WAP gateway providers, and thus cannot guarantee overall service control. Therefore, a need exists for a system that allows a user to change WAP gateways dynamically while in session whereby such a process will also allow tighter and more dynamic control of the quality of service (QoS) on a session-by-session basis.
  • QoS quality of service
  • Wireless applications have enhanced usability when they are integrated with wireless-specific information. This includes support for features such as roaming and market preferences such as pre-paid and pay-per-use support.
  • WAP roaming is currently achieved with one of the following methods.
  • MNOs Mobile Network Operators
  • Service Providers have developed various pre-paid service packages where services are only provided when there are credits in subscribers' pre-purchased accounts. Pre-paid services have become extensively used by subscribers. However, the pre-paid packages are limited to voice services only and currently there are no pre-paid data services available on conventional networks. This is often due to the fact that the system cannot always identify the user and offer the user unique or selective packages. In addition, the single gateway through which the user accesses the data is only capable of processing certain packages that by definition will limit certain services offered to the subscriber.
  • Another concept which is yet to be developed in the wireless data network is the pay-per-use data service.
  • subscribers may or may not sign up with the MNO, but can purchase service as they go, on the basis of usage time or number of accesses. Again, this has not been possible in conventional system due to limitations in the configuration and operation of the system.
  • the current art would restrict or prevent pay-per-use and pre-paid selections to be applied by all applications within a single gateway, thus eliminating the possibility of selective pre-paid application use on a user-by-user or session-by-session basis.
  • the routing table being used to represent a mapping of the subscriber to the current WAP gateway of choice, the service profile or service level associated with the WAP gateway, and the subscriber's individual security and priority profile/level;
  • FIG. 1A shows the existing WAP architecture (Prior art).
  • FIG. 1B shows the security hole problem that exists in the existing WAP architecture (Prior art).
  • FIG. 2 shows an overall block diagram of the novel AirNgine Mobile Service Gateway ( 201 ).
  • FIG. 3 shows a block diagram of the WAP Controller ( 234 ) that is set forth as part of the Service Router ( 230 ) in FIG. 2 .
  • FIG. 4 shows the protocol stack of the WAP Controller ( 234 ) shown in FIG. 3 .
  • FIG. 5 shows the internal data structure of the Routing Table ( 305 ) that is provided within the WAP Controller ( 234 ) of FIG. 3 .
  • FIG. 6 shows the overall data flow of the WAP Controller ( 234 ) of FIG. 3 .
  • FIG. 7 shows the work flow of the UDP Listener ( 301 ) shown in FIG. 3 .
  • FIG. 8 shows the flow chart of a Worker Thread ( 304 ) set forth in FIG. 3 .
  • FIG. 8A shows the flow chart of the Packet Sniffer Thread ( 315 ) set forth in FIG. 3 .
  • FIG. 9 shows the work flow of the Data Feeder Thread ( 307 ) shown in FIG. 3 .
  • FIG. 10 shows the flow diagram of the Management Thread ( 308 ) set forth in FIG. 3 .
  • FIG. 11 shows the flow diagram of Drive Page Thread ( 310 ) of FIG. 3 .
  • FIG. 12 illustrates the message sequence flow from a WAP device to the WAP Controller ( 234 ), Service Selection Management ( 233 ), User&Device Identification ( 232 ) and WAP gateway.
  • FIG. 13 shows the deployment scenarios of the AirNgine MSG ( 201 ) in a wireless network.
  • FIG. 14 depicts the traffic flow through AirNgine MSG ( 201 ) when in a roaming mode of operation.
  • FIG. 15 shows WAP Controller ( 234 ) of FIG. 3 within a wireless network external to data gateway.
  • FIG. 16 shows WAP Controller ( 234 ) of FIG. 3 embedded in a data gateway within a wireless data network.
  • the specific embodiments taught herein set forth an improved WAP system and controller.
  • This system is capable of dynamically allowing a WAP user to change WAP gateways in session or out of session.
  • the system also allows for dynamic selection and application of different service profiles. Due to unique packaging and handling of IP addresses and unique application of the timing and location of encoding and decoding, the WAP security hole problem is reduced or eliminated and security of transmitted data is improved.
  • other benefits are obtained as discussed herein.
  • the WAP system and controller can be better understood with reference to FIGS. 1–16 below.
  • AirNgine Mobile Service Gateway ( 201 )
  • FIG. 2 A high-level block diagram of the AirNgine Mobile Service Gateway (MSG) ( 201 ) platform, which is generally the gateway and controller set forth within the system of FIG. 3 , is as shown in FIG. 2 .
  • MSG AirNgine Mobile Service Gateway
  • the AirNgine MSG ( 201 ) is a service control and policy enforcement element located within in the wireless data network. It is also the integration point between network service entities to which it provides unified access and applications (or end-user services) (e.g., Service Agent ( 220 )). It interacts with:
  • the AirNgine MSG system ( 201 ) generally consists of a base Framework ( 210 ), feature servers (Service Agent ( 220 )), a Service Router ( 230 ), a Subscriber and Service Profile System (SSPS) ( 240 ) and an Operation, Administration, Maintenance and Provisioning (OAM&P) ( 250 ) system.
  • the AirNgine MSG ( 201 ) communicates with network elements through several protocols including, but not limited to, SMPP, SS7/IS41-MAP, SS7/INAP-TCAP and SIP, with applications through an OSA-like API [Ref-11] and natively in WAP with the bearer plane.
  • the Service Agent ( 220 ) in FIG. 2 consists of the following Feature Servers through which it develops wireless smarts for use in both policy enforcement, a unified view to applications, and other functions:
  • the Service Router ( 230 ) enables the following network services:
  • the AirNgine Platform ( 201 ) also has an Operation, Administration, Maintenance and Provisioning OAM&P ( 250 ) System that provides full-feature Fault, Configuration, Accounting and Performance management.
  • the objective of the OAM&P ( 250 ) is to provide this capability for each of the product components.
  • the management layer ( 250 ) will:
  • the system of FIG. 2 is shown in greater detail in FIG. 3 .
  • the contents of the WAP Controller portion ( 234 ) of FIG. 2 is shown in more detail.
  • the present embodiment operates with any wireless data protocol and almost any wireless data network(s) including the existing Second Generation (2G) GSM, TDMA and CDMA Circuit Switched Data (CSD) environment and the forthcoming 2.5G GSM GPRS and CDMA 1XRTT and Third Generation (3G) all-IP wireless data networks as well as other technologies.
  • 2G Second Generation
  • GSM Second Generation
  • CDMA 1XRTT Third Generation
  • the WAP Controller ( 234 ) of FIG. 3 requires, in a preferred embodiment, that WAP devices use its IP address as the WAP gateway address, so that all the WAP requests from the WAP device will be sent to the WAP Controller ( 234 ).
  • WAP traffic can be classified into two categories, namely pull and push.
  • the pull traffic is initiated by a WAP device requesting a service (e.g., prepaid operations, security changes, etc.) or information from a server, whereas the push traffic is generated by a server delivering information to the WAP device without explicit request.
  • Push notifications identify WAP devices by their MSISDN and generally bypass the WAP controller ( 234 ) as shown at a bottom of the FIG. 3 .
  • WAP Controller ( 234 ) generally addresses the pull traffic.
  • the external communications are labeled with protocol names (e.g., WAP/UDP, HTML, etc.).
  • components interact by direct access within the process space with mutual exclusion object (mutex) protection.
  • FIG. 3 shows the structure of the WAP controller while FIG. 6 shows the overall data flow within the WAP Controller ( 234 ).
  • an incoming WAP request ( 601 ) that is received from a WAP Device is first accepted by the User Datagram Protocol (UDP) Listener ( 301 ) (see FIG. 3 for items labeled 3xx in the following paragraphs).
  • the UDP Listener ( 301 ) places the request into the Request Queue ( 303 ) which is picked up by one of the multi-threaded Worker Threads ( 304 ) via steps ( 602 ), ( 603 ), and ( 604 ).
  • UDP User Datagram Protocol
  • the Worker Thread ( 304 ) may identify the request as a service selection request and place it in the Drive Page Queue ( 311 ) ( 606 ), or the Worker Thread ( 304 ) may identify the request as a pass-through request and send it out directly to WAP gateways ( 605 ).
  • the request is picked up by one of the Drive Page Threads ( 310 ) ( 607 ) from the Drive Page Queue ( 309 ) which causes a drive page to be sent back to the WAP device ( 608 ).
  • FIG. 6 shows the entire process of communication within the Controller ( 234 ) that is shown in FIG. 3
  • FIG. 7 shows the specific flow within the UDP Listener Thread ( 301 ) of FIG. 3 when a request is received from the WAP device.
  • the UDP Listener ( 301 ) of FIG. 3 performs the task of accepting WAP traffic in its infinite loop manner until a termination signal is received ( 701 ). It generally listens ( 702 ) at the following UDP and TCP ports for WAP requests from WAP Devices.
  • the UDP Listener ( 301 ) puts the request in an object ( 703 ) together with the WAP device's IP address. To reduce memory allocation/de-allocation, this object is taken from an Object Pool ( 302 ) as shown in FIG. 3 . The object is then placed in a mutual exclusion object protected (mutex-protected) Request Queue ( 303 ) which is monitored by multiple Worker Threads ( 304 ). Note that the listening operation within the UDP Listener ( 301 ) times out after 2 seconds (or some other reasonable time) so that the termination signal can be checked regularly.
  • FIG. 8 shows the flow of the Worker Thread ( 304 ) when the Thread ( 304 ) picks up a WAP request from the Request Queue ( 303 ).
  • a Worker Thread ( 304 ) performs the tasks of:
  • the Worker Thread repeats those tasks for objects within the Request Queue ( 303 ) indefinitely until a termination signal is received ( 801 ).
  • a Worker Thread ( 304 ) performs the following algorithm as shown in FIG. 8 .
  • the Work Threads ( 304 ) are used to determine which requests are to be split off for processing by the Service Selection Management ( 233 ) routine and which requests are to be processed for communication to the WAP gateway.
  • WAP Controller ( 234 ) routes Wireless Transport Layer Security (WTLS) traffic to the destination WAP gateway verbatim.
  • WTLS Wireless Transport Layer Security
  • WTLS specifications [see Ref-6, page 62] usually require the micro-browser on the WAP device to verify whether the Common Name (defined as the IP address or host name) of WAP gateway matches the WAP gateway IP address used in the WAP device. Since the WAP device uses the IP address of WAP Controller ( 234 ), the WAP gateway WTLS certification preferably uses this IP address as its Common Name for security reasons.
  • FIG. 4 shows that a request progressed from a mobile device to a WAP proxy server is layered within one of many different types of protocols.
  • the WAP Controller's Routing Table ( 305 ) may contain millions of entries, comparing with a maximum of 20,000 entries in a standard router. This is especially likely in the 2.5G and 3G environments where WAP devices can be always-on in the IP networks.
  • the Routing Table ( 305 ) in FIG. 3 is thus preferably implemented with a Hash Table ( 501 ) as shown in FIG. 5 with an almost-constant look-up hashing algorithm using IP addresses in their network integer format.
  • the number of the hash buckets is preferably chosen to be a prime number greater than the total number of routing entries. This reduces the potential hashing collision and improves look-up efficiency.
  • FIG. 5 shows the Routing Table's ( 305 ) internal data structure.
  • the hash table elements for each table entry in table ( 501 ) are organized in a Linked List ( 502 ) of multiple entries where appropriate.
  • Each element in the linked list is a Routing Entry ( 503 ) along with a linked list pointer field.
  • Each Routing Entry ( 503 ) contains one or more of the following pieces of information:
  • the Header Name Index ( 504 ) allows each WAP device to have it's preferred subscriber identifier header name ( 511 ).
  • the subscriber identifier ( 508 ) varies depending on user privacy and service provider requirements.
  • the ID can be the MSISDN, a scrambled MSISND (such as an MD 5 digest of the MSISDN), or a common community identifier.
  • the identifier ( 508 ) can also be turned off, i.e. empty in some applications.
  • the QoS Parameters ( 509 ) enables the WAP Controller ( 234 ) to mark WAP traffic using IPv4 TOS (Type of Service) or DS (Differentiated Service) fields to control the quality of service on a per request basis. This QoS Parameter will also work in the future IPv6 environment.
  • the charging parameters ( 510 ) capture both the time based costs and number of access charging models for a given user, mobile device or request.
  • the assigned port numbers are indexed for fast searching by the Packet Sniffer thread ( 315 ). These numbers are used together with the WAP device IP and port to forward returning connection-oriented WAP traffic.
  • the Worker Thread ( 304 ) algorithm in FIG. 8 and the Hash Table ( 501 ) implementation of the Routing Table ( 305 ) are useful for optimizing the efficiency of the WAP Controller ( 234 ).
  • information within the Hash Table entries may be modified in session or per request by the user of the mobile device so that dynamic adjustment of the routing table is possible.
  • both the WAP device and the WAP gateway maintain a connection state.
  • the connection state identifies a valid connection by analyzing the quadruple ⁇ client IP, client port, server IP, server port>. Packets coming from hosts other than that identified by the valid connection state are discarded. Because of the state information, the WAP Controller ( 234 ) has to act as the proxy for the incoming WAP request as well as the returning traffic. Owing to the fact that the WAP Controller ( 234 ) needs to proxy a large number of WAP devices, it is most efficient to assign a distinct port on the WAP Controller ( 234 ) machine to represent the WAP device and routing the return traffic accordingly.
  • the Packet Sniffer thread ( 315 ) performs this task using the routing table with an index on the assigned port.
  • An assigned port is freed when its corresponding WAP device sends an abort request or no WAP traffic is detected over a time-out period (referring to the Management Thread ( 308 )).
  • FIG. 8A shows the flow of the Packet Sniffer thread ( 315 ).
  • the Packet Sniffer thread ( 315 ) repetitively grab packets that are originated from port 9201 or 9203 and targeted at the WAP Controller ( 234 ) IP address ( 8 A 02 ).
  • the packet's target port number is used to retrieve the related routing entry which contains the WAP device IP address and port number ( 8 A 03 ).
  • the Packet Sniffer ( 315 ) rewrites the destination IP and port of the packets and forwards them to the WAP device ( 8 A 05 ). If no matching routing entry is found, the packet is discarded.
  • the Drive Page Thread ( 309 ) is responsible for:
  • FIG. 11 shows the flow of a Drive Page Thread ( 309 ) that is shown in FIG. 3 .
  • Drive Page Threads ( 309 ) run in a perpetual loop until a termination signal is received ( 1101 ). In the loop, the Drive Page Thread ( 309 ) first tests whether its connection to the Service Selection Management ( 233 ) is broken ( 1102 ). If so, it proceeds to re-connect without processing any drive page request ( 1107 ).
  • the Drive Page Thread ( 309 ) picks up a request from the Drive Page Queue ( 310 ) ( 1103 ) and sends it to the Service Selection Management instance ( 233 ) ( 1104 ), the Thread ( 309 ) then checks whether there is any drive page returned from the Service Selection Management ( 233 ). If there is any drive pages returned to the Thread ( 309 ) by the Management module ( 233 ), the drive pages are processed and sent to the WAP device ( 1106 ) for presentation to the mobile device user.
  • the WAP Controller ( 234 ) receives regular updates of routing entries from the Service Selection Management module ( 233 ) and User&Device Identification module ( 232 ) as soon as WAP users log on and off the network.
  • a logging on event signals a new routing entry to be inserted into WAP Controller ( 234 ) Routing Table ( 305 ), whereas a logging off event requires removing the related routing entry from the Routing Table ( 305 ).
  • Routing entry updates are handled by the Data Feeder Thread ( 307 ).
  • the Data Feeder interface ( 311 ) follows the HTTP 1.1 [Ref-10] protocol in a preferred form.
  • FIG. 9 shows the flow of the Data Feeder Thread ( 307 ) of FIG. 3 .
  • the Data Feeder Thread runs in a loop until a termination signal is received ( 901 ).
  • the Thread ( 307 ) first listens for incoming data ( 902 ) from the modules ( 232 ) and ( 235 ). If the incoming data is HTTP PUT, the Thread ( 307 ) proceeds to batch data processing ( 905 ); otherwise the Thread ( 307 ) performs single entry processing ( 904 ). In processing, if the data requires insertion (a log on), the routing entry is inserted into the Routing Table ( 305 ) ( 907 ); if the data require deletion (a log off), the routing entry is deleted from the Routing Table ( 305 ) ( 909 ). After the operation, a success page is sent indicating processing successful ( 911 ). If none of the above applies, a failure page is sent denoting processing failure ( 910 ).
  • the WAP Controller ( 234 ) also supports a management interface (Process 308 and API 314 ).
  • the management API ( 314 ) provides WAP Controller ( 234 ) internal states and statistics in HTML and XML again in HTTP 1.1 protocol in a preferred form.
  • FIG. 10 shows the flow of the Management Thread ( 308 ).
  • the Management Thread ( 308 ) is responsible for one or more of:
  • the Management Thread ( 308 ) operates in a loop until a termination signal is received ( 1001 ).
  • the Thread ( 308 ) first listens for an incoming request ( 1002 ). When a request arrives, it tests whether the request is a status request ( 1003 ). If so, the Management Thread collects operational measurements (OMs), status and states (such as number of requests processed and the number of cached requests) and sends the data in a reply page ( 1005 ), else the command is processed within the Thread ( 308 ) ( 1004 ). If the request is a command (such as “halt”), it sets the termination signal and sends a reply page ( 1006 ).
  • OMs operational measurements
  • status and states such as number of requests processed and the number of cached requests
  • the IWF/GGSN/PDSN When a WAP device logs on the wireless network, the IWF/GGSN/PDSN authenticates the WAP device, authorizes its accesses and also accounts for the log on event. This is done by communicating with the AAA server as shown in FIG. 3 .
  • the IWF/GGSN/PDSN is configured using User&Device Identification ( 232 ) as the AM server.
  • the User & Device Identification ( 232 ) takes an AAA request, extracts the required data and forwards the request to the actual AAA server.
  • Calling-Station-Id represents the MSISDN
  • Framed-IP-Address represents the IP address
  • Acct-Status-Type Start or Stop RADIUS attributes in the Accounting-Request packets.
  • the information maps an IP address to a MSISDN which is pushed to Routing Management ( 235 ) which in turn generates a routing entry and updates the WAP Controller ( 234 ) via the Data Feeder ( 307 ) and the Routing Table ( 305 ).
  • This log on process normally happens before any bearer traffic is started or allowed for that device over the network.
  • the same procedure occurs when a WAP device logs off the network. However, this time the IWF/GGSN/PDSN signals the termination of the session and the Routing Entry ( 503 ) for that WAP device is removed from the Routing Table ( 305 ) of the WAP Controller ( 234 ).
  • Routing Management ( 235 )
  • the Routing Management ( 235 ) stores routing entries persistently and controls the routing entries for the WAP Controller ( 234 ) when WAP devices log on and off the wireless network.
  • a WAP Controller ( 234 ) starts up, it requests the Routing Management ( 235 ) to fill the Routing Table ( 305 ) over the HTTP interface ( 311 ) shown in FIG. 3 .
  • Routing Management ( 235 ) pushes routing entries to the WAP Controller ( 234 ) accordingly in the event that WAP devices log on the network. Routing Management ( 235 ) uses the following strategies to formulate routing entries within the routing table ( 305 ).
  • WAP Controller ( 234 ) When WAP Controller ( 234 ) needs to provide a drive page, it makes a request to the Service Selection Management ( 233 ) of FIG. 2 along with the WAP device's IP address from the Routing Table ( 305 ).
  • the Service Selection Management ( 233 ) generates a drive page based on user preferences, user group, service subscription which are retrieved from SSPS ( 240 ) in FIG. 2 , and wireless intelligence (such as location, roaming, pre-paid account, etc.) which are obtained from the Service Agent ( 220 ) in FIG. 2 .
  • the OAM&P ( 250 ) in AirNgine MSG ( 201 ) of FIG. 2 allows comprehensive provisioning from Mobile Network Operations (MNOs), Service Providers and end users.
  • the provisioned data is stored in SSPS ( 240 ).
  • all the HTTP interfaces in the WAP Controller support the efficient HTTP/1.1 pipelining as outlined in [Ref-10].
  • FIG. 12 shows an example signal flow sequence and message sequence flow from WAP device to the WAP Controller ( 234 ) and WAP gateway from log on and sessions start to session end.
  • FIG. 12 is not discussed in detail since it largely summarizes most of the information already discussed with reference to FIGS. 3–11 .
  • FIG. 13 shows the deployment scenarios of the WAP Controller into a wireless network wherein the WAP Controller can dynamically change a session or user device between a plurality of Gateways. Deployment works with GSM/TDMA/CDMA circuit switched data (CSD), GSM and TDMA GPRS, as well as all future IP core networks. Note that the router connected to the WAP controller ( 234 ) can dynamically switch access and service between many different WAP gateways and Web Servers, or communicate with multiple gateways in parallel. With the system of FIG. 13 using the Controller of FIGS. 3–12 , a multiple-profile system is possible where a user may create multiple profiles where each profile contains a unique WAP gateway IP address, NAS (Network Access Server) dialup number, user ID and password.
  • NAS Network Access Server
  • the subscriber when switching to a new application, the subscriber need not terminate the current session.
  • the current session can be maintained and the profile changed without significant interruption using the system taught herein.
  • the wireless network operators now has control over user's selection on WAP gateway providers and thus can guarantee overall service control.
  • the WAP Controller ( 234 ) performs a common function in a wireless data network, it can also be embedded in a data gateway within a wireless data network, as shown in FIG. 16 (compared with the WAP Controller ( 234 ) deployed external to the data gateway as shown in FIG. 15 ). This flexibility allows a Controller ( 234 ) to enable differentiated service for WAP traffic in several different configurations.
  • FIG. 3 The system set forth in FIG. 3 and operationally discussed per FIGS. 4–12 may perform several functions. These functions are set forth below.
  • the WAP Controller ( 234 ) does not need to be exposed to the Internet with a public IP address.
  • the WAP Controllers ( 234 ) can be configured with the same private IP addresses (such as, 10.0.0.0) in all the networks.
  • a Mobile Station (MS) always uses the same IP address as the WAP gateway address in both the home and foreign networks. In other words, the IP address of the MS is static. Given the set and static IP addresses in the MS, the WAP Controller ( 234 ) can route every WAP requests back to the home network WAP gateway with ease.
  • FIG. 14 shows the traffic flow in the roaming scenario whereby an MS in a foreign network can route, by IP addresses, all necessary information directly to the home network hardware and software.
  • the WAP Controller ( 234 ) is located at the best position to handle prepaid and pay-per-use data service because it intercepts WAP traffic after subscribers get into the MNO network but before they reach any services (WAP gateway access, QoS and transport end points, etc.). Therefore, the WAP Controller ( 234 ) will enforce pre-paid and pay-per-use criteria (i.e. time and number of accesses) when traffic is passing through on a per subscriber or per session basis. Therefore, the system taught herein provides useful elements and advantages when offering pre-paid and pay-per-use data services to mobile device or WAP subscribers.

Abstract

A method (FIG. 5) and apparatus (FIG. 3) to provide control and policy enforcement of WAP (Wireless Application Protocol) services in a wireless data networks is taught herein. WAP traffic is inspected with efficient algorithms to intercept un-registered WAP access and intercept dynamic change of user service selection. The intercepted WAP requests are modified with value-added parameters (such as QoS and subscriber identifiers) as per user and service provider agreement and table data. A series of strategies are described to blend wireless intelligence, user preference and service subscription, network operator requirements and service provider or enterprise preferences into routing and drive page generation. The means to dynamically provision users' service choices to wireless network elements are also presented without having to break the session within the system. This enables innovative data services such as pay-per-use, smart routing, and enterprise secured WAP services unlike any current conventional system.

Description

CROSS REFERENCES
For background information this patent refers to the following publications,
  • [Ref-1] “Wireless Application Protocol (WAP) Specification”, version 1.2.1, June 2000, WAP Forum. http://www.wapforum.com/what/technical.htm
  • [Ref-2] “WAP Wireless Session Protocol Specification”, version 4 May 2000, WAP Forum. pp. 63–70.
  • [Ref-3] “WAP Wireless Transaction Protocol Specification”, version 19 Feb. 2000, WAP Forum, pp. 22–66.
  • [Ref-4] “WAP Wireless Datagram Protocol Specification”, version 19 Feb. 2000, WAP Forum, pp. 23–50.
  • [Ref-5] “WAP Architecture Specification”, version 30 Apr. 1998, WAP Forum.
  • [Ref-6] “WAP Wireless Transport Layer Security Specification”, version 18 Feb. 2000, WAP Forum.
  • [Ref-7] “User Datagram Protocol”, IETF RFC-768, 28 Aug. 1980.
  • [Ref-8] “Internet Protocol”, IETF RFC-791, September 1981.
  • [Ref-10] “Hypertext Transfer Protocol—HTTP/1.1”, IETF RFC-2068, January 1997.
  • [Ref-11] “Open Service Architecture, Application Programming Interface—Part 1 (Release 1999)”, 3GPP TS 29.198 V3.2.0, 3rd Generation Partnership Project; December 2000.
  • [Ref-12] “WAP Architecture Specification 2.0”, WAP Forum, October 2000.
BRIEF SUMMARY—FIELD OF EMBODIMENT
The embodiments disclosed herein relate to the development and use of a smart controller to provide dynamic service selection, policing, redirection and management of WAP (Wireless Application Protocol) traffic, or like wireless data traffic, in a wireless data network. In particular the embodiments relates to:
  • 1. The development of a dynamic integrated subscriber WAP routing table (305) of FIG. 3 that combines subscriber's individual service profile, the subscriber's WAP-gateway selection and the WAP-gateway's service profiles.
  • 2. The use and application of the above “table” along with various subscriber identifiers to enable an efficient method of inspecting WAP traffic in the system of FIG. 3, entitled “WAP Controller”, to dynamically alter the subscriber serving WAP gateway without session interruption (see FIG. 13).
  • 3. The use of the above WAP Controller of FIG. 3 to provide simultaneous access to multiple WAP gateways during a single data session (also referred to as Service Selection).
  • 4. The use of the above WAP Controller of FIG. 3 to enable new wireless data service parameters to be developed and dynamically implemented (example Roaming support, pre-paid and pay-per-use data services) and the enforcement of traffic behaviors on WAP traffic depending on different service/subscriber profiles.
BACKGROUND—DESCRIPTION OF PRIOR ART
WAP (Wireless Application Protocol) Architecture
WAP (Wireless Application Protocol) is a standard proposed by the WAP Forum (http://www.wapforum.org) [Ref-1, Ref-5] that allows information to be sent and received by wireless devices. WAP has been deployed in several existing cellular wireless data networks (e.g., GSM, TDMA and CDMA).
WAP capable wireless devices (WAP devices) have several operational constraints compared to traditional Internet access devices such as personal computers. These limitations include a less powerful CPU, less memory, restricted power consumption, smaller display, and different input methods to the device. In addition, WAP devices operate in an environment that generally provides less bandwidth, less connection stability, less predictable availability, and greater latency than their wire-line counterparts. With these considerations, the WAP Forum introduced a new network element called the WAP Gateway that was targeted at addressing one or more of these issues.
In a traditional browser environment the processing and caching takes place in a single location with the display being located adjacent to the data handling. The WAP gateway splits this process acting as a proxy (i.e. hosting default home page, recording cookies, content and protocol conversions, etc.) for the devices as shown in FIG. 1A. In addition, the WAP gateway has been forced to provide several adjacent functions that assist in the end-to-end flow of data as part of the bridging or proxy function that they perform in the wireless network.
Another prior art concept is the unique identification of subscriber in the IP and wireless domains. However, due to privacy concerns, the WAP standard does not allow the device to send in a unique identifier in its requests, where one such identifier may be the phone number of the device, commonly referred as the MSISDN (Mobile Subscriber ISDN number). This inability to transmit an ID poses a serious challenge to the application development on the Web server which does not have a consistent means to identify the WAP device and hence the user. The solution, from application development side, is to require the user to log on by typing a user ID or MSISDN plus a password. Owing to the limited capability of the input method on the device, this is both inconvenient and difficult. Therefore, a need exists for a more convenient and simple way to allow WAP or wireless data requests to be tagged with IDs so that services can be differentiated on a request-by-request basis, a user-by-user basis, or a device-by-device basis, since this function is desirable and is not possible using conventional devices.
WAP gateway vendors have developed solutions to obtain IP address to MSISDN mapping from the NAS (Network Access Server) or AAA (Authentication, Authorization and Accounting) server. The WAP gateway then can identify each WAP request by the IP address and pass the MSISDN either in the URL or the HTTP header to applications running on Web servers. This requires the WAP gateway to collocate with the NAS or AAA in the carrier domain, which limits the configuration possibilities of the system. Enterprises and Wireless Portals who would like to control user experience by owning the WAP gateway will not have access to this critical information in the NAS or AAA, whereby flexibility within the system is lost when using this approach.
Another prior art method involves using the service control in existing WAP implementations. In existing wireless data networks the choice of WAP application is established through:
    • 1. WAP page selection system; or
    • 2. Multiple-profile system.
In the WAP page selection system, the subscriber is presented multiple origin server choices through a single WAP gateway (WAP implementations/protocol associate a WAP device with a single WAP gateway).
The IP address of the WAP gateway is embedded in the WAP device restricting the device from accessing any other end-point directly and forcing one single WAP gateway to provide all services to the WAP device. This severely restricts the flexibility and scope of services that may be provided to the end user. In summary, this type of a system results in two major problems:
    • 1. A security problem known as the WAP security hole; and
    • 2. A service problem where the services that are provided to the subscriber are undifferentiated or inflexible.
      WAP Security Hole
In a traditional WAP session a data request is encrypted by the WAP device and transmitted over the WAP device to the WAP gateway using the Wireless Transport Layer Security (WTLS) protocol [Ref-6]. The WAP gateway is then forced to decrypt the message and then re-encrypt it using another protocol (e.g. Secure Socket Layer) before transmitting it to the data content site origin server (FIG. 1B). The WTLS certificate only authenticates the WAP device to the WAP gateway. Therefore, to ensure end-to-end authentication, the WAP gateway would need to reside on the content site. However, the presence of an embedded WAP gateway IP address in the WAP device forces the subscriber to break connection with the network, re-program the IP address in the WAP device for each separate WAP service access. For mission-critical applications that demand high data security, it's desirable to have the WAP gateway co-located with the application. Therefore, a different manner of delivering encrypted WAP traffic is needed to ensure that the WAP security hole problem is solved or at least reduced in severity.
Undifferentiated Service
When subscribers access applications through a single WAP gateway, the network service level they receive is limited by the service tier of the WAP gateway (which is the primary network element). As a result, in centralized WAP gateway deployments, both critical and casual applications have the same bandwidth allocation, the same latency, and the same security parameters associated with them in a single service tier. In order for individual application bundles to be associated with differentiated service tiers a unique WAP gateway needs to be coupled with each bundle. The combination of the applications plus the network service level then creates a “WAP service level”.
In a conventional multiple-profile system, the subscriber defines multiple profiles with each profile containing a unique WAP gateway IP address, NAS (Network Access Server) dialup number, user ID and password. Unfortunately, switching to a new application, forces the subscriber to terminate the current session, modify the profile choice, and start a new session. Dynamically changing the WAP gateway provider within the same session is impossible using conventional techniques and systems. The process to create multiple profiles is cumbersome, tedious, and technically challenging. In addition, wireless network operators have no control over a user's selection on WAP gateway providers, and thus cannot guarantee overall service control. Therefore, a need exists for a system that allows a user to change WAP gateways dynamically while in session whereby such a process will also allow tighter and more dynamic control of the quality of service (QoS) on a session-by-session basis.
Wireless Data—Parameter Support
Wireless applications have enhanced usability when they are integrated with wireless-specific information. This includes support for features such as roaming and market preferences such as pre-paid and pay-per-use support.
Roaming
WAP roaming is currently achieved with one of the following methods.
    • User making long distance calls to the home networks that incurs a huge cost to the user, and is therefore unpopular.
    • Upgrading the NAS/RAS server in the roaming network to tunnel back to the home network, which is complex and inflexible.
    • Using a foreign WAP gateway to access the home WAP portals without accessing back to the home network. This methodology loses the user identity at the home WAP system and substantially discounts the user experience.
    • Using a local dial-up ISP to access the WAP gateway in the home network. Again the user identity will be lost in this approach.
All the existing approaches to roaming are either cost inefficient, unnecessarily complex, and/or substantially reduce the user experience. In addition the prior art does not recognize or provide the ability to provide local services selectively when in a roamed network, largely due to the fact that, in most cases, the user identity is lost.
Pre-Paid and Pay-per-use Support for Wireless Data Services
Mobile Network Operators (MNOs) and Service Providers have developed various pre-paid service packages where services are only provided when there are credits in subscribers' pre-purchased accounts. Pre-paid services have become extensively used by subscribers. However, the pre-paid packages are limited to voice services only and currently there are no pre-paid data services available on conventional networks. This is often due to the fact that the system cannot always identify the user and offer the user unique or selective packages. In addition, the single gateway through which the user accesses the data is only capable of processing certain packages that by definition will limit certain services offered to the subscriber.
Another concept which is yet to be developed in the wireless data network is the pay-per-use data service. In this scenario, subscribers may or may not sign up with the MNO, but can purchase service as they go, on the basis of usage time or number of accesses. Again, this has not been possible in conventional system due to limitations in the configuration and operation of the system.
The current art would restrict or prevent pay-per-use and pre-paid selections to be applied by all applications within a single gateway, thus eliminating the possibility of selective pre-paid application use on a user-by-user or session-by-session basis.
ADVANTAGES OF THE EMBODIMENT
Accordingly, several advantages of the disclosed embodiments are to provide a system and methodology that has one or more of the following aspects:
To provide a system and method for developing an integrated subscriber WAP-gateway routing table. The routing table being used to represent a mapping of the subscriber to the current WAP gateway of choice, the service profile or service level associated with the WAP gateway, and the subscriber's individual security and priority profile/level;
To provide a system and method for each service selection choice to be individually monitored in a dynamic manner so that further requests are appropriately serviced and service is flexible;
To provide a system and method for subscribers to be presented WAP service choices on-demand, each of which represents a different WAP gateway and hence a different service tiers or different quality of service (QoS);
To provide a system and apparatus that allows subscribers to simultaneously access multiple WAP gateways during a single data session;
To provide a system and apparatus that provides an efficient inspection of WAP traffic and enables the WAP-user to dynamically alter his WAP service selection at any time, in or out of session;
To provide a system and apparatus that provides a WAP content provider unique and secure subscriber identification in conjunction with dynamic service selection for the subscriber;
To provide a system and apparatus that enforces different traffic behaviors on WAP traffic depending on the subscriber selection, subscriber profile and Service Agreement;
To provide a system and apparatus that combines Service Selection with a Subscriber and Service Profile System thus enabling new wireless data service parameters to be developed and implemented (example Roaming support and pre-paid/pay-per-use data services) to create more personalized services;
To provide a system and method that affords mobile network operators the capability of offering tiered WAP service with differentiators such as QoS, routing over differentiated transport layers and with value-add information (e.g. inserting subscriber identifier);
To optimize identification of out-going non-WTLS WAP traffic (i.e. from WAP device to WAP gateway) with efficient algorithms and to minimize latency by allowing the returning traffic routed directly to the WAP device.
To generally improve upon WAP, or like wireless, data systems.
Other features and advantages of the present embodiment will become apparent from the following detailed description, in conjunction with the accompanying drawings.
BRIEF DESCRIPTIONS OF THE DRAWINGS
FIG. 1A shows the existing WAP architecture (Prior art).
FIG. 1B shows the security hole problem that exists in the existing WAP architecture (Prior art).
FIG. 2 shows an overall block diagram of the novel AirNgine Mobile Service Gateway (201).
FIG. 3 shows a block diagram of the WAP Controller (234) that is set forth as part of the Service Router (230) in FIG. 2.
FIG. 4 shows the protocol stack of the WAP Controller (234) shown in FIG. 3.
FIG. 5 shows the internal data structure of the Routing Table (305) that is provided within the WAP Controller (234) of FIG. 3.
FIG. 6 shows the overall data flow of the WAP Controller (234) of FIG. 3.
FIG. 7 shows the work flow of the UDP Listener (301) shown in FIG. 3.
FIG. 8 shows the flow chart of a Worker Thread (304) set forth in FIG. 3.
FIG. 8A shows the flow chart of the Packet Sniffer Thread (315) set forth in FIG. 3.
FIG. 9 shows the work flow of the Data Feeder Thread (307) shown in FIG. 3.
FIG. 10 shows the flow diagram of the Management Thread (308) set forth in FIG. 3.
FIG. 11 shows the flow diagram of Drive Page Thread (310) of FIG. 3.
FIG. 12 illustrates the message sequence flow from a WAP device to the WAP Controller (234), Service Selection Management (233), User&Device Identification (232) and WAP gateway.
FIG. 13 shows the deployment scenarios of the AirNgine MSG (201) in a wireless network.
FIG. 14 depicts the traffic flow through AirNgine MSG (201) when in a roaming mode of operation.
FIG. 15 shows WAP Controller (234) of FIG. 3 within a wireless network external to data gateway.
FIG. 16 shows WAP Controller (234) of FIG. 3 embedded in a data gateway within a wireless data network.
PREFERRED EMBODIMENT—DETAILED DESCRIPTION
Generally, the specific embodiments taught herein set forth an improved WAP system and controller. This system is capable of dynamically allowing a WAP user to change WAP gateways in session or out of session. The system also allows for dynamic selection and application of different service profiles. Due to unique packaging and handling of IP addresses and unique application of the timing and location of encoding and decoding, the WAP security hole problem is reduced or eliminated and security of transmitted data is improved. In addition, other benefits are obtained as discussed herein. Specifically, the WAP system and controller can be better understood with reference to FIGS. 1–16 below.
AirNgine Mobile Service Gateway (201)
A high-level block diagram of the AirNgine Mobile Service Gateway (MSG) (201) platform, which is generally the gateway and controller set forth within the system of FIG. 3, is as shown in FIG. 2.
The AirNgine MSG (201) is a service control and policy enforcement element located within in the wireless data network. It is also the integration point between network service entities to which it provides unified access and applications (or end-user services) (e.g., Service Agent (220)). It interacts with:
  • bearer traffic elements (e.g. IWF, GGSN) (as shown in more detail in FIG. 3),
  • network elements that provide access to wireless information (e.g. MPC), and
  • end-user services/applications resident either in the PLMN space or on the Service Provider premise.
The AirNgine MSG system (201) generally consists of a base Framework (210), feature servers (Service Agent (220)), a Service Router (230), a Subscriber and Service Profile System (SSPS) (240) and an Operation, Administration, Maintenance and Provisioning (OAM&P) (250) system. The AirNgine MSG (201) communicates with network elements through several protocols including, but not limited to, SMPP, SS7/IS41-MAP, SS7/INAP-TCAP and SIP, with applications through an OSA-like API [Ref-11] and natively in WAP with the bearer plane.
    • The Framework (210) consists of the following primary functions:
    • Registration Routine (211): Performs user and service registration where a user can register himself or a wireless device and various services associated therewith, and change such selections over time in some embodiments.
    • Discovery Routine (212): Allows other components to discover new users and services being published and notifies interested components within the system of the new user or services.
    • Authentication Routine (213): This sub-portion is used to authenticate both users and service providers within the system. Single sign-on (removal of double authentication) will usually depend on the service provider-to-operator Service Level Agreement.
    • Authorization Routine (214): Provides access to network resources based on static and dynamic service provider profiles.
    • Usage Accounting Routine (215): Provides transaction-based logging of access to any network resource for use by the billing system (e.g. Call Detail Record (CDR)).
    • Prioritization Routine (216): Provides differentiated or prioritized use of feature servers (see Service Agent (220)) depending on service provider/subscriber profiles.
The Service Agent (220) in FIG. 2 consists of the following Feature Servers through which it develops wireless smarts for use in both policy enforcement, a unified view to applications, and other functions:
    • Presence Server (221): Identifies when and whether the subscriber is available for communication flows. This integrates concepts of “buddy lists” and time-of-day (user preference), service priorities and network capabilities (alert message delivery in a multimedia flow) so that users are getting messages when and where they want.
    • Roaming Server (222): provides out-of-the-box roaming support creating a seamless environment for service presentment and usage by routing mobile device traffic back to the home network whereby the mobile device uses a single fixed IP address.
    • Connectivity Server (223): Creates the appropriate Virtual Private Network (VPN)/tunnel for an application thus supporting the concept of layer integration. Provide router-provisioning capability for setting up parameters such as tunnels, filtering, Network Address Translation (NAT) as described in the service profile via COPS-PR, Simple Network Management Protocol (SNMP), CLI.
    • Messaging Server (224): Allows send/receive messages to be processed to/from the mobile device over Short Message Service (SMS). The server interoperates with an SMSC for delivering the SMS messages over SMPP.
    • Location Server (225): Gathers subscriber location information by interacting with the appropriate network elements (e.g. MPC (Mobile Positioning Center)/PDE (Position Determining Equipment), HLR (Home Location Register)).
The Service Router (230) enables the following network services:
    • Policy Services (231): Provides service redirection using a coordinated Policy Server with Radius/Diameter, COPS, HTTP/XML interface to the Data Gateway (PDSN/xGSN). Policies are integrated with:
      • Wireless smarts delivered through feature server support such as presence, roaming and location;
      • Subscriber and service profile systems;
      • Enhanced DNS/Redirection Name Server;
      • Push Policy Enforcement Parameters to Data Gateway (VPN, QOS, Data Rates/Bandwidth) using the Connectivity server; and
      • AAA functions, such as radius/AAA client proxy.
    • User and Device Identification (232): Derives user and/or device identification by decoding networking level identification. Since the Mobile Service Gateway (MSG) (201) is interested in identifying a subscriber in both wireless and data worlds it needs to create a unique mapping to the MSISDN.
    • Service Selection Management (233): Provides,
      • 1. Drive pages for dynamic user service selection (i.e. providing one-click menus or selections to user wireless devices or PDA/device for accessing different web services like prepayment options and data security)—with MAS function support;
      • 2. Access control (based on policy/user or content provider subscription arrangement/agreement). A Single Sign-On methodology is possible;
      • 3. Authentication/clearing house (for data on demand access, pre-paid data services, etc.)—with MAS function support;
    • WAP Controller (234): The Controller is responsible for the flow of WAP traffic to far-end gateways and enables easy development of personalized WAP services. This module is described in much more detail in FIGS. 3–12. It allows an MVNO (Mobile Virtual Network Operator)/enterprise to own the WAP Gateway and provide user (e.g. cookies) and content selection (e.g. top deck). By moving the WAP Gateway into enterprises or financial institutions behind a firewall or like protection (see FIG. 13 where the WAP Gateway is located behind a firewall), the security gap between WTLS and HTTS (the “WAP security hole”) is literally plugged and entirely eliminated. This is created with a seamless upgrade path with no impact/changes on existing WAP devices, WAP gateways or applications
    • The Subscriber and Service Profile System (SSPS) (240):
    • The SSPS (240) stores all the subscriber and service profiles and the rules associated with them. Other components interact with the SSPS (240) via Lightweight Directory Access Protocol (LDAP) and/or Common Object Request Broker Architecture (CORBA) interface.
The AirNgine Platform (201) also has an Operation, Administration, Maintenance and Provisioning OAM&P (250) System that provides full-feature Fault, Configuration, Accounting and Performance management. The objective of the OAM&P (250) is to provide this capability for each of the product components. The management layer (250) will:
    • Be agnostic of the underlying management protocol, e.g., SNMP or device/application specific protocols.
    • Take advantage of industry standard framework such as JMX/JDMK.
    • Have the same look and feel as SSPS (240).
    • Define Management Information Bases (MIBs) for each managed entity and allow the MIBs to be registered at run-time with the management system.
      WAP Controller (234)
The system of FIG. 2 is shown in greater detail in FIG. 3. Specifically, in FIG. 3, the contents of the WAP Controller portion (234) of FIG. 2 is shown in more detail. The present embodiment operates with any wireless data protocol and almost any wireless data network(s) including the existing Second Generation (2G) GSM, TDMA and CDMA Circuit Switched Data (CSD) environment and the forthcoming 2.5G GSM GPRS and CDMA 1XRTT and Third Generation (3G) all-IP wireless data networks as well as other technologies.
The WAP Controller (234) of FIG. 3 requires, in a preferred embodiment, that WAP devices use its IP address as the WAP gateway address, so that all the WAP requests from the WAP device will be sent to the WAP Controller (234). WAP traffic can be classified into two categories, namely pull and push. The pull traffic is initiated by a WAP device requesting a service (e.g., prepaid operations, security changes, etc.) or information from a server, whereas the push traffic is generated by a server delivering information to the WAP device without explicit request. Push notifications identify WAP devices by their MSISDN and generally bypass the WAP controller (234) as shown at a bottom of the FIG. 3. WAP Controller (234) generally addresses the pull traffic. In FIG. 3, the external communications are labeled with protocol names (e.g., WAP/UDP, HTML, etc.). Within the WAP Controller (234), components interact by direct access within the process space with mutual exclusion object (mutex) protection.
FIG. 3 shows the structure of the WAP controller while FIG. 6 shows the overall data flow within the WAP Controller (234). In FIG. 6, an incoming WAP request (601) that is received from a WAP Device is first accepted by the User Datagram Protocol (UDP) Listener (301) (see FIG. 3 for items labeled 3xx in the following paragraphs). The UDP Listener (301) places the request into the Request Queue (303) which is picked up by one of the multi-threaded Worker Threads (304) via steps (602), (603), and (604). The Worker Thread (304) may identify the request as a service selection request and place it in the Drive Page Queue (311) (606), or the Worker Thread (304) may identify the request as a pass-through request and send it out directly to WAP gateways (605). In the event that the request is a service selection request, the request is picked up by one of the Drive Page Threads (310) (607) from the Drive Page Queue (309) which causes a drive page to be sent back to the WAP device (608).
UDP Listener (301)
While FIG. 6 shows the entire process of communication within the Controller (234) that is shown in FIG. 3, FIG. 7 shows the specific flow within the UDP Listener Thread (301) of FIG. 3 when a request is received from the WAP device. The UDP Listener (301) of FIG. 3 performs the task of accepting WAP traffic in its infinite loop manner until a termination signal is received (701). It generally listens (702) at the following UDP and TCP ports for WAP requests from WAP Devices.
9200: WAP connectionless session service
9201: WAP session service
9202: WAP secure connectionless session service
9203: WAP secure session service
9204: WAP vcard
9205: WAP vCal
9206: WAP vCard Secure
9207: WAP vCal Secure
When a WAP request arrives from a device, the UDP Listener (301) puts the request in an object (703) together with the WAP device's IP address. To reduce memory allocation/de-allocation, this object is taken from an Object Pool (302) as shown in FIG. 3. The object is then placed in a mutual exclusion object protected (mutex-protected) Request Queue (303) which is monitored by multiple Worker Threads (304). Note that the listening operation within the UDP Listener (301) times out after 2 seconds (or some other reasonable time) so that the termination signal can be checked regularly.
Worker Thread (304)
Once objects are placed into the Request Queue (303) as discussed per FIG. 7, FIG. 8 shows the flow of the Worker Thread (304) when the Thread (304) picks up a WAP request from the Request Queue (303). Generally, a Worker Thread (304) performs the tasks of:
    • analyzing WSP (Wireless Session Protocol) headers from the object,
    • determining whether a request in an object is a service selection request, a service selection reply or a pass through traffic that is to be sent out to a WAP Gateway,
    • routing flow-through traffic (e.g., traffic to WAP Gateways),
    • enforcing pre-paid/pay-per-use rules, and/or
    • performing IP Quality of Service (QoS) packet marking.
The Worker Thread repeats those tasks for objects within the Request Queue (303) indefinitely until a termination signal is received (801).
More specifically, when a request is obtained from Request Queue (303) (802), a Worker Thread (304) performs the following algorithm as shown in FIG. 8.
    • 1. The Worker Thread (304) first checks whether the request is a Wireless Transport Layer Security (WTLS) request (803). If so, it checks whether the IP address is in the Routing Table (305) (810). If so, it goes to step 5 (812), otherwise it's an error (811).
    • 2. The Worker Thread (304) analyzes the Uniform Resource Locator (URL) in the WAP request (804). If the request contains a special URL (e.g. http://DrivePage/) (805) indicating the request for drive page (813), the Worker Thread removes the routing entry from Routing Table (305) and places the request in the Drive Page Queue (311) (813). The request is then considered served for the Worker Thread (304).
    • 3. If the source IP address of the request is in the Routing Table (305) (806), and if the account balance is in order (i.e. within the purchased time and number of access limits) (809), the Worker Thread (304) inserts a subscriber identifier from the routing table (305) into the WAP request header (e.g. DEVICE_PHONE_NUMBER: MSISDN) (814) and moves on to the step 5 (812). If the account balance is over due, a drive page is delivered (808) to notify the user of the balance problem.
    • 4. If the source IP address is not in the Routing Table (305) in step (806), the Worker Thread (304) checks whether the request contains service selection reply URL (e.g. http://Select/CommunityName/) (807). If not, the request is placed in the Drive Page Queue (311) (808) and the request is also stored in Request Cache (306). Otherwise, the worker thread retrieves the cached WAP request from Request Cache (306) and validates the service selection (816). If the selection is valid (817), the Worker Thread generates a corresponding routing entry (818), informs Service Selection Management of the user's choice, and takes the cached request through the steps (818, 815, and 812). Otherwise, the drive page needs to be displayed to the WAP user again (808) by placing the request in the Drive Page Queue (311).
    • 5. Step (812) creates an IP packet with the WAP gateway IP address as the destination IP and the receiving source port as the destination port. For connectionless WAP traffic (port 9200 and 9202), the system uses the WAP device IP address as the source IP and device port as source port. For connection-oriented WAP traffic (port 9201 and 9203), the system uses the WAP controller IP address as the source IP and a free port on the WAP Controller as the source port. The system then sends out the packet and updates the newly assigned port (applicable in connection-oriented mode) and charging parameters within the applicable routing entry. Related CDRs (Call Detail Records) and OMs (Operational Measurements) are generated.
In summary, the Work Threads (304) are used to determine which requests are to be split off for processing by the Service Selection Management (233) routine and which requests are to be processed for communication to the WAP gateway.
Returning to FIG. 3, and in a preferred form, WAP Controller (234) routes Wireless Transport Layer Security (WTLS) traffic to the destination WAP gateway verbatim. For security reasons, WTLS specifications [see Ref-6, page 62] usually require the micro-browser on the WAP device to verify whether the Common Name (defined as the IP address or host name) of WAP gateway matches the WAP gateway IP address used in the WAP device. Since the WAP device uses the IP address of WAP Controller (234), the WAP gateway WTLS certification preferably uses this IP address as its Common Name for security reasons.
The details of the WAP Controller (234) protocol stack are shown in FIG. 4 [Ref-4]. FIG. 4 shows that a request progressed from a mobile device to a WAP proxy server is layered within one of many different types of protocols.
Routing Table (305)
In FIG. 3, because there is no concept of subnets, the WAP Controller's Routing Table (305) may contain millions of entries, comparing with a maximum of 20,000 entries in a standard router. This is especially likely in the 2.5G and 3G environments where WAP devices can be always-on in the IP networks. The Routing Table (305) in FIG. 3 is thus preferably implemented with a Hash Table (501) as shown in FIG. 5 with an almost-constant look-up hashing algorithm using IP addresses in their network integer format. The number of the hash buckets is preferably chosen to be a prime number greater than the total number of routing entries. This reduces the potential hashing collision and improves look-up efficiency.
FIG. 5 shows the Routing Table's (305) internal data structure. The hash table elements for each table entry in table (501) are organized in a Linked List (502) of multiple entries where appropriate. Each element in the linked list is a Routing Entry (503) along with a linked list pointer field. Each Routing Entry (503) contains one or more of the following pieces of information:
    • A WAP device IP address (505),
    • Its chosen WAP gateway (G/W) IP address (506),
    • A preferred subscriber identifier header name index (507) that can be used to identify the community in which the subscriber belongs,
    • The subscriber identifier (508),
    • A QoS parameter (509),
    • Charging parameters (510),
    • WAP device port number (511), and
    • Assigned port number (512).
The Header Name Index (504) (see also (507)) allows each WAP device to have it's preferred subscriber identifier header name (511). The subscriber identifier (508) varies depending on user privacy and service provider requirements. The ID can be the MSISDN, a scrambled MSISND (such as an MD5 digest of the MSISDN), or a common community identifier. The identifier (508) can also be turned off, i.e. empty in some applications. The QoS Parameters (509) enables the WAP Controller (234) to mark WAP traffic using IPv4 TOS (Type of Service) or DS (Differentiated Service) fields to control the quality of service on a per request basis. This QoS Parameter will also work in the future IPv6 environment. The charging parameters (510) capture both the time based costs and number of access charging models for a given user, mobile device or request. The assigned port numbers are indexed for fast searching by the Packet Sniffer thread (315). These numbers are used together with the WAP device IP and port to forward returning connection-oriented WAP traffic.
The Worker Thread (304) algorithm in FIG. 8 and the Hash Table (501) implementation of the Routing Table (305) are useful for optimizing the efficiency of the WAP Controller (234). In addition, information within the Hash Table entries may be modified in session or per request by the user of the mobile device so that dynamic adjustment of the routing table is possible.
Packet Sniffer (315)
In the connection-oriented mode, both the WAP device and the WAP gateway maintain a connection state. The connection state identifies a valid connection by analyzing the quadruple <client IP, client port, server IP, server port>. Packets coming from hosts other than that identified by the valid connection state are discarded. Because of the state information, the WAP Controller (234) has to act as the proxy for the incoming WAP request as well as the returning traffic. Owing to the fact that the WAP Controller (234) needs to proxy a large number of WAP devices, it is most efficient to assign a distinct port on the WAP Controller (234) machine to represent the WAP device and routing the return traffic accordingly. The Packet Sniffer thread (315) performs this task using the routing table with an index on the assigned port. An assigned port is freed when its corresponding WAP device sends an abort request or no WAP traffic is detected over a time-out period (referring to the Management Thread (308)).
FIG. 8A shows the flow of the Packet Sniffer thread (315). The Packet Sniffer thread (315) repetitively grab packets that are originated from port 9201 or 9203 and targeted at the WAP Controller (234) IP address (8A02). The packet's target port number is used to retrieve the related routing entry which contains the WAP device IP address and port number (8A03). With this information, the Packet Sniffer (315) rewrites the destination IP and port of the packets and forwards them to the WAP device (8A05). If no matching routing entry is found, the packet is discarded.
Drive Page Thread (309)
In FIG. 3, the Drive Page Thread (309) is responsible for:
    • sending drive page requests to Service Selection Management (223),
    • returning the drive pages back to the WAP devices, and
    • load balancing multiple Service Selection Managements (223).
There are usually multiple Drive Page Threads (309) running in the system of FIG. 3. Each thread (309) connects to an instance of the Service Selection Management (223) module and is used to process drive page requests for service selection back to the mobile device. FIG. 11 shows the flow of a Drive Page Thread (309) that is shown in FIG. 3. Drive Page Threads (309) run in a perpetual loop until a termination signal is received (1101). In the loop, the Drive Page Thread (309) first tests whether its connection to the Service Selection Management (233) is broken (1102). If so, it proceeds to re-connect without processing any drive page request (1107). When the connection is fine, the Drive Page Thread (309) picks up a request from the Drive Page Queue (310) (1103) and sends it to the Service Selection Management instance (233) (1104), the Thread (309) then checks whether there is any drive page returned from the Service Selection Management (233). If there is any drive pages returned to the Thread (309) by the Management module (233), the drive pages are processed and sent to the WAP device (1106) for presentation to the mobile device user.
Data Feeder (307)
The WAP Controller (234) receives regular updates of routing entries from the Service Selection Management module (233) and User&Device Identification module (232) as soon as WAP users log on and off the network. A logging on event signals a new routing entry to be inserted into WAP Controller (234) Routing Table (305), whereas a logging off event requires removing the related routing entry from the Routing Table (305). Routing entry updates are handled by the Data Feeder Thread (307). The Data Feeder interface (311) follows the HTTP 1.1 [Ref-10] protocol in a preferred form.
FIG. 9 shows the flow of the Data Feeder Thread (307) of FIG. 3. The Data Feeder Thread runs in a loop until a termination signal is received (901). The Thread (307) first listens for incoming data (902) from the modules (232) and (235). If the incoming data is HTTP PUT, the Thread (307) proceeds to batch data processing (905); otherwise the Thread (307) performs single entry processing (904). In processing, if the data requires insertion (a log on), the routing entry is inserted into the Routing Table (305) (907); if the data require deletion (a log off), the routing entry is deleted from the Routing Table (305) (909). After the operation, a success page is sent indicating processing successful (911). If none of the above applies, a failure page is sent denoting processing failure (910).
Management Thread (308)
The WAP Controller (234) also supports a management interface (Process 308 and API 314). The management API (314) provides WAP Controller (234) internal states and statistics in HTML and XML again in HTTP 1.1 protocol in a preferred form. FIG. 10 shows the flow of the Management Thread (308). In particular, the Management Thread (308) is responsible for one or more of:
    • monitoring other threads. Launching and killing worker threads (304),
    • responding to heartbeat, operational measurements (OMs), and status requests,
    • cleaning up stale requests in the Request Cache (306),
    • freeing unused assigned ports, and
    • updating the internal clock.
Like other threads, the Management Thread (308) operates in a loop until a termination signal is received (1001). In FIG. 10, the Thread (308) first listens for an incoming request (1002). When a request arrives, it tests whether the request is a status request (1003). If so, the Management Thread collects operational measurements (OMs), status and states (such as number of requests processed and the number of cached requests) and sends the data in a reply page (1005), else the command is processed within the Thread (308) (1004). If the request is a command (such as “halt”), it sets the termination signal and sends a reply page (1006).
User & Device Identification (232)
When a WAP device logs on the wireless network, the IWF/GGSN/PDSN authenticates the WAP device, authorizes its accesses and also accounts for the log on event. This is done by communicating with the AAA server as shown in FIG. 3. In FIG. 3, the IWF/GGSN/PDSN is configured using User&Device Identification (232) as the AM server. The User & Device Identification (232) takes an AAA request, extracts the required data and forwards the request to the actual AAA server. Interesting parameters in an AAA record include Calling-Station-Id (represents the MSISDN), Framed-IP-Address (represents the IP address) and Acct-Status-Type (Start or Stop) RADIUS attributes in the Accounting-Request packets. The information maps an IP address to a MSISDN which is pushed to Routing Management (235) which in turn generates a routing entry and updates the WAP Controller (234) via the Data Feeder (307) and the Routing Table (305). This log on process normally happens before any bearer traffic is started or allowed for that device over the network. The same procedure occurs when a WAP device logs off the network. However, this time the IWF/GGSN/PDSN signals the termination of the session and the Routing Entry (503) for that WAP device is removed from the Routing Table (305) of the WAP Controller (234).
Routing Management (235)
In FIG. 3, the Routing Management (235) stores routing entries persistently and controls the routing entries for the WAP Controller (234) when WAP devices log on and off the wireless network. When a WAP Controller (234) starts up, it requests the Routing Management (235) to fill the Routing Table (305) over the HTTP interface (311) shown in FIG. 3.
The Routing Management (235) pushes routing entries to the WAP Controller (234) accordingly in the event that WAP devices log on the network. Routing Management (235) uses the following strategies to formulate routing entries within the routing table (305).
    • Default Routing:
    • If the WAP device has a preferred WAP gateway and takes that gateway as the default all the time, the preferred WAP gateway is used in the Routing Entry (503). This is most useful with a wireless carrier supporting multiple Mobile Virtual Network Operators (MVNOs), enterprises, or portals. The default gateway can change depending on carrier requirement, e.g. special maintenance schedule or network modifications.
    • Last Choice Routing:
    • Routing based on user's previous service selection with a user chosen expiration time.
    • Roaming Routing:
    • When a WAP device is roaming in the carrier network and there's a roaming agreement with the WAP device's home network WAP gateway identified as the preferred, the WAP device's home network WAP gateway is chosen.
    • General Routing:
    • When there is no apparent routing strategy, the Routing Management module will not push any Routing Entry (503) to the WAP Controller (234). The IP address to MSISDN mapping is stored in the User & Device Identification (232) to be used when the first WAP request comes from the WAP device.
      Service Selection Management (233)
When WAP Controller (234) needs to provide a drive page, it makes a request to the Service Selection Management (233) of FIG. 2 along with the WAP device's IP address from the Routing Table (305). The Service Selection Management (233) generates a drive page based on user preferences, user group, service subscription which are retrieved from SSPS (240) in FIG. 2, and wireless intelligence (such as location, roaming, pre-paid account, etc.) which are obtained from the Service Agent (220) in FIG. 2. The OAM&P (250) in AirNgine MSG (201) of FIG. 2 allows comprehensive provisioning from Mobile Network Operations (MNOs), Service Providers and end users. The provisioned data is stored in SSPS (240).
In a preferred form, all the HTTP interfaces in the WAP Controller support the efficient HTTP/1.1 pipelining as outlined in [Ref-10].
FIG. 12 shows an example signal flow sequence and message sequence flow from WAP device to the WAP Controller (234) and WAP gateway from log on and sessions start to session end. FIG. 12 is not discussed in detail since it largely summarizes most of the information already discussed with reference to FIGS. 3–11.
FIG. 13 shows the deployment scenarios of the WAP Controller into a wireless network wherein the WAP Controller can dynamically change a session or user device between a plurality of Gateways. Deployment works with GSM/TDMA/CDMA circuit switched data (CSD), GSM and TDMA GPRS, as well as all future IP core networks. Note that the router connected to the WAP controller (234) can dynamically switch access and service between many different WAP gateways and Web Servers, or communicate with multiple gateways in parallel. With the system of FIG. 13 using the Controller of FIGS. 3–12, a multiple-profile system is possible where a user may create multiple profiles where each profile contains a unique WAP gateway IP address, NAS (Network Access Server) dialup number, user ID and password. However, when switching to a new application, the subscriber need not terminate the current session. The current session can be maintained and the profile changed without significant interruption using the system taught herein. In addition, the wireless network operators now has control over user's selection on WAP gateway providers and thus can guarantee overall service control.
Because the WAP Controller (234) performs a common function in a wireless data network, it can also be embedded in a data gateway within a wireless data network, as shown in FIG. 16 (compared with the WAP Controller (234) deployed external to the data gateway as shown in FIG. 15). This flexibility allows a Controller (234) to enable differentiated service for WAP traffic in several different configurations.
The system set forth in FIG. 3 and operationally discussed per FIGS. 4–12 may perform several functions. These functions are set forth below.
Roaming Support
Unlike conventional WAP gateways, the WAP Controller (234) does not need to be exposed to the Internet with a public IP address. In the situation where a carrier operates multiple networks in different countries or carriers with roaming agreements, the WAP Controllers (234) can be configured with the same private IP addresses (such as, 10.0.0.0) in all the networks. A Mobile Station (MS) always uses the same IP address as the WAP gateway address in both the home and foreign networks. In other words, the IP address of the MS is static. Given the set and static IP addresses in the MS, the WAP Controller (234) can route every WAP requests back to the home network WAP gateway with ease. This way, WAP roaming becomes seamless by provisioning roaming users in the SSPS (240) with quick access to the users' home network WAP gateway(s). Consistent personalized services can be assured by ensuring that all roaming traffic is sent directly back to the home Gateway whereby the tables, ID, and information of the home Gateway is accessed and applied, regardless of roaming location. FIG. 14 shows the traffic flow in the roaming scenario whereby an MS in a foreign network can route, by IP addresses, all necessary information directly to the home network hardware and software. As one advantage to this system, user information is not lost when roaming, and the user experience when in a foreign network will be just as if the user was present in his home network.
Pre-Paid and Pay-per-use Support
The WAP Controller (234) is located at the best position to handle prepaid and pay-per-use data service because it intercepts WAP traffic after subscribers get into the MNO network but before they reach any services (WAP gateway access, QoS and transport end points, etc.). Therefore, the WAP Controller (234) will enforce pre-paid and pay-per-use criteria (i.e. time and number of accesses) when traffic is passing through on a per subscriber or per session basis. Therefore, the system taught herein provides useful elements and advantages when offering pre-paid and pay-per-use data services to mobile device or WAP subscribers.
While the WAP system and methods herein are taught, described, and illustrated with reference to specific implementations, further modifications and improvements will occur to those skilled in the art. For example, the system and methods taught herein can work for other wireless technology standards and methods other than WAP. It is to be understood, therefore, that the claims should not be limited to the particular forms and embodiments illustrated herein and that it is intended that the appended claims cover all modifications that do not depart from the spirit and scope of this invention.

Claims (20)

1. A wireless system comprising:
a mobile user device that is programmable so that it can be associated with multiple user profiles; and
a controller coupled to service sessions, having data traffic, between the mobile user device and one or more gateways and servers that handle wireless requests, wherein controller allows the user to change from a first user profile to a second user profile within a session via selections made on the mobile user device without requiring termination of the session, which results in switching data traffic of the mobile user device from one wireless gateway to another wireless gateway;
wherein a user profile contains at least a unique WAP gateway IP address, NAS (Network Access Server) dialup number, and user.
2. The system of claim 1 wherein the changing of a user profile results in changing a gateway with which the mobile user device is communicating in order to communicate with multiple gateways in parallel.
3. A wireless system for processing wireless requests, the system comprising:
a controller coupled to service sessions between the mobile user device and one or more wireless gateways and servers that handle wireless requests; and
a service selection management program coupled to the controller, wherein the controller provides service selection information to the service selection management program and the service selection management program communicates with the mobile user device to allow service selections to be dynamically changed while a wireless session is being conducted, and wherein subscriber identifiers and other parameters are placed into the wireless request to identify the changing service requirements.
4. The system of claim 3 wherein the wireless device identifiers set user security levels for wireless data transmissions.
5. A wireless system for processing wireless requests, the system comprising:
a controller coupled to service sessions between the mobile user device and one or more wireless gateways and servers that handle wireless requests; and
a service selection management program coupled to the controller,
wherein the controller provides service selection information to the service selection management program to allow the operator to dynamically establish differentiated revenue models with tiered services based on one or more of a geo-position of the mobile user device, data packet quality of service (QoS), transport security settings, network loading or prioritized resource utilization levels.
6. A wireless system for processing wireless requests, the system comprising:
a controller coupled to service sessions between the mobile user device and one or more servers that handle wireless requests;
a service selection management program coupled to the controller; and
a plurality of wireless gateways that handle wireless requests and are connected between the controller and the one or more servers wherein the service selection management program monitors information associated with a wireless session to determine selectively which wireless gateway is to process that wireless session.
7. The system of claim 6 wherein the service selection management program is capable of intelligent service-dependent routing of WAP traffic based on mobile user device roaming, mobile user device location, user identification, or WAP service selection.
8. The system of claim 6 wherein the system inserts a subscriber identifier in all non-WTLS WAP requests.
9. The system of claim 6 wherein a plurality of the wireless gateways are enabled in parallel to each other to process a request from mobile user device.
10. A wireless system using a routing table, the routing table comprising:
a table of table entries stored in memory within the system;
each table entry within the table being capable of pointing to one or more routing entries; and
one or more routing entries coupled to one or more table entries;
wherein each routing entry contains all of: a device address and port, a gateway address, a subscriber ID, a quality of service parameter, an assigned proxy port and charging parameters ordered linked list; hash table.
11. A wireless system using a routing table, the routing table comprising:
a table of table entries stored in memory within the system;
each table entry within the table being capable of pointing to one or more routing entries; and
one or more routing entries coupled to one or more table entries, wherein each routing entry contains one or more of a device address and port, a gateway address, a subscriber ID, a quality of service parameter, an assigned proxy port and charging parameters;
wherein the table is a hash table and the routing entries are connected as a serial ordered linked lists when more than one routing entry is associated with a single table entry.
12. A wireless system using a routing table, the routing table comprising:
a table of table entries stored in memory within the system;
each table entry within the table being capable of pointing to one or more routing entries; and
one or more routing entries coupled to one or more table entries, wherein each routine entry contains one or more of a device address and port, a gateway address, a subscriber ID, a quality of service parameter, an assigned proxy port and charging parameters;
wherein a wireless device user can dynamically change one or more of the entries of their routing entry while in session.
13. A wireless system using a routing table, the routing table comprising:
a table of table entries stored in memory within the system;
each table entry within the table being capable of pointing to one or more routing entries; and
one or more routing entries coupled to one or more table entries, wherein each routing entry contains one or more of a device address and port, a gateway address, a subscriber ID, a quality of service parameter, an assigned proxy port and charging parameters;
wherein the routing table represents a mapping of the subscriber to a current WAP gateway of choice wherein that WAP gateway may be changed by changing information in the routing table.
14. A wireless system using a routing table, the routing table comprising:
a table of table entries stored in memory within the system;
each table entry within the table being capable of pointing to one or more routing entries; and
one or more routing entries coupled to one or more table entries, wherein each routing entry contains one or more of a device address and port, a gateway address, a subscriber ID, a quality of service parameter, an assigned proxy port and charging parameters;
wherein the routing table represents the service profile or service level associated with a WAP gateway and a subscriber's individual security and priority profile/level wherein this information may be dynamically changed by the subscriber.
15. A wireless system having a controller, the controller comprising:
an input routine for receiving information from a wireless device;
worker threads for processing requests received through the input routine and either obtaining data from external gateways in response to the requests or providing requests to a service management module to process service selection for the wireless device;
a routing table for use by the worker threads when processing requests; and drive page threads for providing data back to wireless devices in response to processed requests.
16. The system of claim 15 wherein data within memory and associated with each wireless device may be changed so that some of the wireless devices are associated with a variety of payment schemes.
17. The system of claim 15 wherein data within the system for each wireless device may be changed so that some of the wireless devices access a first gateway while other wireless devices access a second gateway.
18. The system of claim 15 wherein service choices for a wireless device may be made on demand by changing information within the routing table.
19. The system of claim 15 wherein each wireless device is assigned a unique identifier in the routing table and dynamic services may be selected and changed using that unique identifier.
20. A method to support consistent parameters and service settings while roaming within a wireless system, the method comprising:
fixing a static IP address within a mobile device;
receiving, in a foreign network, a request from the mobile device where the request is associated with the static IP address;
forwarding the request from the foreign network to a wireless gateway within the home network using the static IP address; and
processing, within the home network, the request using parameters and service settings stored within the home network.
US09/933,781 2001-08-20 2001-08-20 Method and apparatus for providing service selection, redirection and managing of subscriber access to multiple WAP (Wireless Application Protocol) gateways simultaneously Active 2024-05-12 US7039037B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US09/933,781 US7039037B2 (en) 2001-08-20 2001-08-20 Method and apparatus for providing service selection, redirection and managing of subscriber access to multiple WAP (Wireless Application Protocol) gateways simultaneously

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US09/933,781 US7039037B2 (en) 2001-08-20 2001-08-20 Method and apparatus for providing service selection, redirection and managing of subscriber access to multiple WAP (Wireless Application Protocol) gateways simultaneously

Publications (2)

Publication Number Publication Date
US20030035409A1 US20030035409A1 (en) 2003-02-20
US7039037B2 true US7039037B2 (en) 2006-05-02

Family

ID=25464490

Family Applications (1)

Application Number Title Priority Date Filing Date
US09/933,781 Active 2024-05-12 US7039037B2 (en) 2001-08-20 2001-08-20 Method and apparatus for providing service selection, redirection and managing of subscriber access to multiple WAP (Wireless Application Protocol) gateways simultaneously

Country Status (1)

Country Link
US (1) US7039037B2 (en)

Cited By (150)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030095555A1 (en) * 2001-11-16 2003-05-22 Mcnamara Justin System for the validation and routing of messages
US20030105873A1 (en) * 2001-11-30 2003-06-05 Oracle Corporation Servicing requests that are issued in a protocol other than the protocol expected by the service
US20030131311A1 (en) * 2001-11-16 2003-07-10 Mcnamara Justin Methods and systems for tracking and playing back errors in a communications network
US20030187996A1 (en) * 2001-11-16 2003-10-02 Cardina Donald M. Methods and systems for routing messages through a communications network based on message content
US20040024894A1 (en) * 2002-08-02 2004-02-05 Osman Fazil Ismet High data rate stateful protocol processing
US20040083296A1 (en) * 2002-10-25 2004-04-29 Metral Max E. Apparatus and method for controlling user access
US20040093381A1 (en) * 2002-05-28 2004-05-13 Hodges Donna Kay Service-oriented architecture systems and methods
US20040148384A1 (en) * 2003-01-23 2004-07-29 Karthik Ramakrishnan Method for implementing an internet protocol (IP) charging and rating middleware platform and gateway system
US20040199648A1 (en) * 2003-04-01 2004-10-07 Art Shelest Network zones
US20040252657A1 (en) * 2003-06-16 2004-12-16 Shailesh Lakhani Method and system for multimedia messaging service (MMS) rating and billing
US20040258031A1 (en) * 2003-06-19 2004-12-23 Zabawskyj Bohdan Konstantyn Method for implemening a Wireless Local Area Network (WLAN) gateway system
US20050091377A1 (en) * 2001-11-30 2005-04-28 Ralph Behrens Browser-enabled communication system and client and server for one such communication system
US20050117602A1 (en) * 2002-05-13 2005-06-02 Michael Carrigan Control of PLMN messaging services in IP domains
US20050204035A1 (en) * 2004-03-12 2005-09-15 Dan Kalish System and method for identifying content service within content server
US20060075014A1 (en) * 2004-09-29 2006-04-06 Intel Corporation Method and apparatus for securing devices in a network
US20070005770A1 (en) * 2005-06-30 2007-01-04 Bea Systems, Inc. System and method for managing communications sessions in a network
US20070106800A1 (en) * 2005-11-04 2007-05-10 Bea Systems, Inc. System and method for controlling access to legacy push protocols based upon a policy
US20070104186A1 (en) * 2005-11-04 2007-05-10 Bea Systems, Inc. System and method for a gatekeeper in a communications network
US20070124797A1 (en) * 2003-07-25 2007-05-31 Rajiv Gupta Policy based service management
US20070133574A1 (en) * 2005-12-01 2007-06-14 Tekelec Methods, systems, and computer program products for using an E.164 number (ENUM) database for message service message routing resolution among 2G and subsequent generation network systems
US20070168913A1 (en) * 2003-01-02 2007-07-19 Sekhar Sarukkai Integration of context-sensitive run-time metrics into integrated development environments
US20070208860A1 (en) * 2006-03-02 2007-09-06 Zellner Samuel N User specific data collection
US20070208861A1 (en) * 2006-03-02 2007-09-06 Zellner Samuel N User preference interpretation
US20080027943A1 (en) * 2006-07-31 2008-01-31 Clemens Jonathan P Location-aware network access method and apparatus
US20080059635A1 (en) * 2006-08-31 2008-03-06 Redknee Inc. Policy services
DE102006051652A1 (en) * 2006-11-02 2008-05-08 Deutsche Telekom Ag Parameters changing method for use during connection e.g. analog telephone, of participant with Internet, involves converting instructions into other instructions according to protocol, and supplying instructions to computer
US20080127232A1 (en) * 2006-05-17 2008-05-29 Bea Systems, Inc. Diameter Protocol and SH Interface Support for SIP Server Architecture
US20080137832A1 (en) * 2006-12-07 2008-06-12 Tekelec Methods, systems, and computer program products for providing quality of service using E.164 number mapping (ENUM) data in a communications network
US20080147551A1 (en) * 2006-12-13 2008-06-19 Bea Systems, Inc. System and Method for a SIP Server with Online Charging
US20080147524A1 (en) * 2006-12-13 2008-06-19 Bea Systems, Inc. System and Method for a SIP Server with Offline Charging
US20080155310A1 (en) * 2006-10-10 2008-06-26 Bea Systems, Inc. SIP server architecture fault tolerance and failover
US20080189421A1 (en) * 2006-05-16 2008-08-07 Bea Systems, Inc. SIP and HTTP Convergence in Network Computing Environments
US20080235361A1 (en) * 2007-03-21 2008-09-25 David Crosbie Management layer method and apparatus for dynamic assignment of users to computer resources
US7464148B1 (en) * 2004-01-30 2008-12-09 Juniper Networks, Inc. Network single entry point for subscriber management
US20080311917A1 (en) * 2007-06-15 2008-12-18 Tekelec Methods, systems, and computer program products for identifying a serving home subscriber server (HSS) in a communications network
US20080316939A1 (en) * 2003-12-26 2008-12-25 Vodafone K.K. Presence Display System and Gateway Apparatus
US20090019108A1 (en) * 2007-07-11 2009-01-15 International Business Machines Corporation System and method for application server/operating system network/configuration management
US20090019158A1 (en) * 2006-05-16 2009-01-15 Bea Systems, Inc. Engine Near Cache for Reducing Latency in a Telecommunications Environment
US20090019155A1 (en) * 2007-07-11 2009-01-15 Verizon Services Organization Inc. Token-based crediting of network usage
US20090043704A1 (en) * 2007-08-10 2009-02-12 Tekelec Methods, systems, and computer program products for performing message deposit transaction screening
US20090157754A1 (en) * 2001-11-16 2009-06-18 David Patron System for the Centralized Storage of Wireless Customer Information
US7568107B1 (en) * 2003-08-20 2009-07-28 Extreme Networks, Inc. Method and system for auto discovery of authenticator for network login
US20090227276A1 (en) * 2008-03-07 2009-09-10 Devesh Agarwal Methods, systems, and computer readable media for routing a message service message through a communications network
US20100205335A1 (en) * 2004-04-20 2010-08-12 Lexar Media Inc. Direct secondary device interface by a host
US20100205539A1 (en) * 2009-02-12 2010-08-12 Amivox Ehf. Instant messaging and telephony value added services
US20100223555A1 (en) * 2006-03-02 2010-09-02 At&T Intellectual Property I, L.P. Environment Independent User Preference Communication
US7793334B2 (en) 2001-11-16 2010-09-07 At&T Mobility Ii Llc System and method for password protecting a distribution list
US7792053B1 (en) 2002-07-08 2010-09-07 At&T Intellectual Property Ii, L.P. System for accessing end-to-end broadband network via network access server platform
US7802001B1 (en) * 2002-10-18 2010-09-21 Astute Networks, Inc. System and method for flow control within a stateful protocol processing system
US20100250662A1 (en) * 2009-03-25 2010-09-30 Devesh Agarwal Methods, systems, and computer readable media for providing home subscriber server (hss) proxy
US7814218B1 (en) 2002-10-17 2010-10-12 Astute Networks, Inc. Multi-protocol and multi-format stateful processing
US20100285800A1 (en) * 2009-05-11 2010-11-11 Mccann Thomas M Methods, systems, and computer readable media for providing scalable number portability (np) home location register (hlr)
US20110047225A1 (en) * 2000-04-11 2011-02-24 Smith Richard A Short message distribution center
US20110082779A1 (en) * 2007-09-13 2011-04-07 Redknee Inc. Billing profile manager
US20110085531A1 (en) * 2000-04-11 2011-04-14 Smith Richard A Intellegent delivery agent for short message distribution center
US20110116382A1 (en) * 2009-10-16 2011-05-19 Mccann Thomas M Methods, systems, and computer readable media for providing diameter signaling router with integrated monitoring functionality
US20110312300A1 (en) * 2006-03-02 2011-12-22 Andrew Silver Mobile application gateway for connecting devices on a cellular network with individual enterprise and data networks
US8116275B2 (en) 2005-10-13 2012-02-14 Trapeze Networks, Inc. System and network for wireless network monitoring
US8150357B2 (en) 2008-03-28 2012-04-03 Trapeze Networks, Inc. Smoothing filter for irregular update intervals
US8151278B1 (en) 2002-10-17 2012-04-03 Astute Networks, Inc. System and method for timer management in a stateful protocol processing system
US8161278B2 (en) 2005-03-15 2012-04-17 Trapeze Networks, Inc. System and method for distributing keys in a wireless network
US8171466B2 (en) 2006-05-16 2012-05-01 Oracle International Corporation Hitless application upgrade for SIP server architecture
US8218449B2 (en) 2005-10-13 2012-07-10 Trapeze Networks, Inc. System and method for remote monitoring in a wireless network
US8238298B2 (en) 2008-08-29 2012-08-07 Trapeze Networks, Inc. Picking an optimal channel for an access point in a wireless network
US8238942B2 (en) 2007-11-21 2012-08-07 Trapeze Networks, Inc. Wireless station location detection
US20120317284A1 (en) * 2009-01-28 2012-12-13 Headwater Partners I Llc Adaptive Ambient Services
US8340110B2 (en) * 2006-09-15 2012-12-25 Trapeze Networks, Inc. Quality of service provisioning for wireless networks
US20130040703A1 (en) * 2009-01-28 2013-02-14 Headwater Partner I, LLC Device Assisted Ambient Services
US8396075B2 (en) 2002-12-02 2013-03-12 Redknee Inc. Method for implementing an open charging (OC) middleware platform and gateway system
US20130109378A1 (en) * 2009-01-28 2013-05-02 Headwater Partners I Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US20130122821A1 (en) * 2010-07-05 2013-05-16 Telefonaktiebolaget L M Ericsson L M Ericsson (Pub Power consumption reduction in a user terminal
US8457031B2 (en) 2005-10-13 2013-06-04 Trapeze Networks, Inc. System and method for reliable multicast
US8547908B2 (en) 2011-03-03 2013-10-01 Tekelec, Inc. Methods, systems, and computer readable media for enriching a diameter signaling message
US8548428B2 (en) 2009-01-28 2013-10-01 Headwater Partners I Llc Device group partitions and settlement platform
US8589541B2 (en) 2009-01-28 2013-11-19 Headwater Partners I Llc Device-assisted services for protecting network capacity
US8606911B2 (en) 2009-03-02 2013-12-10 Headwater Partners I Llc Flow tagging for service policy implementation
US8626115B2 (en) 2009-01-28 2014-01-07 Headwater Partners I Llc Wireless network service interfaces
US8634805B2 (en) 2009-01-28 2014-01-21 Headwater Partners I Llc Device assisted CDR creation aggregation, mediation and billing
US8634821B2 (en) 2009-01-28 2014-01-21 Headwater Partners I Llc Device assisted services install
US8635335B2 (en) 2009-01-28 2014-01-21 Headwater Partners I Llc System and method for wireless network offloading
US8638762B2 (en) 2005-10-13 2014-01-28 Trapeze Networks, Inc. System and method for network integrity
US8644355B2 (en) 2010-12-23 2014-02-04 Tekelec, Inc. Methods, systems, and computer readable media for modifying a diameter signaling message directed to a charging function node
US8660537B2 (en) 2001-11-16 2014-02-25 At&T Mobility Ii Llc System for the storage and retrieval of messages
US8670383B2 (en) 2006-12-28 2014-03-11 Trapeze Networks, Inc. System and method for aggregation and queuing in a wireless network
US8725123B2 (en) 2008-06-05 2014-05-13 Headwater Partners I Llc Communications device with secure data path processing agents
US8745191B2 (en) 2009-01-28 2014-06-03 Headwater Partners I Llc System and method for providing user notifications
US8750292B2 (en) 2010-02-25 2014-06-10 Tekelec, Inc. Systems, methods, and computer readable media for using a signaling message routing node to provide backup subscriber information management service
US8751647B1 (en) 2001-06-30 2014-06-10 Extreme Networks Method and apparatus for network login authorization
US8793758B2 (en) 2009-01-28 2014-07-29 Headwater Partners I Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US8818322B2 (en) 2006-06-09 2014-08-26 Trapeze Networks, Inc. Untethered access point mesh system and method
US8832777B2 (en) 2009-03-02 2014-09-09 Headwater Partners I Llc Adapting network policies based on device service processor configuration
US8831016B2 (en) 2011-03-18 2014-09-09 Tekelec, Inc. Methods, systems, and computer readable media for configurable diameter address resolution
US8855654B2 (en) 2013-01-28 2014-10-07 Tekelec Global, Inc. Methods, systems, and computer readable media for tracking and communicating long term evolution (LTE) handset communication capability
US8874743B1 (en) * 2003-05-06 2014-10-28 Juniper Networks, Inc. Systems and methods for implementing dynamic subscriber interfaces
US8893009B2 (en) 2009-01-28 2014-11-18 Headwater Partners I Llc End user device that secures an association of application to service policy with an application certificate check
US8898293B2 (en) 2009-01-28 2014-11-25 Headwater Partners I Llc Service offer set publishing to device agent with on-device service selection
US8902904B2 (en) 2007-09-07 2014-12-02 Trapeze Networks, Inc. Network assignment based on priority
US8918520B2 (en) 2001-03-02 2014-12-23 At&T Intellectual Property I, L.P. Methods and systems for electronic data exchange utilizing centralized management technology
US8924543B2 (en) 2009-01-28 2014-12-30 Headwater Partners I Llc Service design center for device assisted services
US8924469B2 (en) 2008-06-05 2014-12-30 Headwater Partners I Llc Enterprise access control and accounting allocation for access networks
US20150006723A1 (en) * 2013-06-28 2015-01-01 Alcatel-Lucent Canada Inc. Traffic detection function based on usage based thresholds
US8964747B2 (en) 2006-05-03 2015-02-24 Trapeze Networks, Inc. System and method for restricting network access using forwarding databases
US8966018B2 (en) 2006-05-19 2015-02-24 Trapeze Networks, Inc. Automated network device configuration and network deployment
US8978105B2 (en) 2008-07-25 2015-03-10 Trapeze Networks, Inc. Affirming network relationships and resource access via related networks
US9059871B2 (en) 2007-12-27 2015-06-16 Redknee Inc. Policy-based communication system and method
US9094311B2 (en) 2009-01-28 2015-07-28 Headwater Partners I, Llc Techniques for attribution of mobile device data traffic to initiating end-user application
US9100796B2 (en) 2011-12-15 2015-08-04 Tekelec, Inc. Methods, systems, and computer readable media for seamless roaming between diameter and non-diameter networks
US9154826B2 (en) 2011-04-06 2015-10-06 Headwater Partners Ii Llc Distributing content and service launch objects to mobile devices
US9191799B2 (en) 2006-06-09 2015-11-17 Juniper Networks, Inc. Sharing data between wireless switches system and method
US9198042B2 (en) 2009-01-28 2015-11-24 Headwater Partners I Llc Security techniques for device assisted services
US9247450B2 (en) 2009-01-28 2016-01-26 Headwater Partners I Llc Quality of service for device assisted services
US9253663B2 (en) 2009-01-28 2016-02-02 Headwater Partners I Llc Controlling mobile device communications on a roaming network based on device state
US9258702B2 (en) 2006-06-09 2016-02-09 Trapeze Networks, Inc. AP-local dynamic switching
US20160072696A1 (en) * 2014-09-05 2016-03-10 Telefonaktiebolaget L M Ericsson (Publ) Forwarding table precedence in sdn
US9351193B2 (en) 2009-01-28 2016-05-24 Headwater Partners I Llc Intermediate networking devices
US9392462B2 (en) 2009-01-28 2016-07-12 Headwater Partners I Llc Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy
US9557889B2 (en) 2009-01-28 2017-01-31 Headwater Partners I Llc Service plan design, user interfaces, application programming interfaces, and device management
US9565707B2 (en) 2009-01-28 2017-02-07 Headwater Partners I Llc Wireless end-user device with wireless data attribution to multiple personas
US9571559B2 (en) 2009-01-28 2017-02-14 Headwater Partners I Llc Enhanced curfew and protection associated with a device group
US9572019B2 (en) 2009-01-28 2017-02-14 Headwater Partners LLC Service selection set published to device agent with on-device service selection
US9578182B2 (en) 2009-01-28 2017-02-21 Headwater Partners I Llc Mobile device and service management
US9584959B2 (en) 2008-11-24 2017-02-28 Tekelec Global, Inc. Systems, methods, and computer readable media for location-sensitive called-party number translation in a telecommunications network
US9609510B2 (en) 2009-01-28 2017-03-28 Headwater Research Llc Automated credential porting for mobile devices
US9647918B2 (en) 2009-01-28 2017-05-09 Headwater Research Llc Mobile device and method attributing media services network usage to requesting application
US9706061B2 (en) 2009-01-28 2017-07-11 Headwater Partners I Llc Service design center for device assisted services
US9755842B2 (en) 2009-01-28 2017-09-05 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US9858559B2 (en) 2009-01-28 2018-01-02 Headwater Research Llc Network service plan design
US9954975B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Enhanced curfew and protection associated with a device group
US9955332B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Method for child wireless device activation to subscriber account of a master wireless device
US9980146B2 (en) 2009-01-28 2018-05-22 Headwater Research Llc Communications device with secure data path processing agents
US10057775B2 (en) 2009-01-28 2018-08-21 Headwater Research Llc Virtualized policy and charging system
US10064055B2 (en) 2009-01-28 2018-08-28 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US10200541B2 (en) 2009-01-28 2019-02-05 Headwater Research Llc Wireless end-user device with divided user space/kernel space traffic policy system
US10237757B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc System and method for wireless network offloading
US10248996B2 (en) 2009-01-28 2019-04-02 Headwater Research Llc Method for operating a wireless end-user device mobile payment agent
US10264138B2 (en) 2009-01-28 2019-04-16 Headwater Research Llc Mobile device and service management
US10326800B2 (en) 2009-01-28 2019-06-18 Headwater Research Llc Wireless network service interfaces
US10492102B2 (en) 2009-01-28 2019-11-26 Headwater Research Llc Intermediate networking devices
US10715342B2 (en) 2009-01-28 2020-07-14 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US10779177B2 (en) 2009-01-28 2020-09-15 Headwater Research Llc Device group partitions and settlement platform
US10783581B2 (en) 2009-01-28 2020-09-22 Headwater Research Llc Wireless end-user device providing ambient or sponsored services
US10798252B2 (en) 2009-01-28 2020-10-06 Headwater Research Llc System and method for providing user notifications
US10841839B2 (en) 2009-01-28 2020-11-17 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US10897521B2 (en) 2017-01-19 2021-01-19 Advanced New Technologies Co., Ltd. Application-based data interaction method and apparatus
US11218854B2 (en) 2009-01-28 2022-01-04 Headwater Research Llc Service plan design, user interfaces, application programming interfaces, and device management
US11405846B2 (en) 2006-03-02 2022-08-02 Tango Networks, Inc. Call flow system and method for use in a legacy telecommunication system
US11412366B2 (en) 2009-01-28 2022-08-09 Headwater Research Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US11638126B2 (en) 2006-03-02 2023-04-25 Tango Networks, Inc. System and method for enabling call originations using SMS and hotline capabilities
US11849380B2 (en) 2006-03-02 2023-12-19 Tango Networks, Inc. Call flow system and method for use in a VoIP telecommunication system
US11929907B2 (en) 2022-03-08 2024-03-12 T-Mobile Usa, Inc. Endpoint assisted selection of routing paths over multiple networks

Families Citing this family (112)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9590996B2 (en) 1995-06-01 2017-03-07 Netmotion Wireless Holdings, Inc. Multi-network seamless roaming mobile router with auto-discovery and migration of downstream devices on the mobile network
US7103574B1 (en) * 1999-03-27 2006-09-05 Microsoft Corporation Enforcement architecture and method for digital rights management
SE0002572D0 (en) * 2000-07-07 2000-07-07 Ericsson Telefon Ab L M Communication system
US7502929B1 (en) * 2001-10-16 2009-03-10 Cisco Technology, Inc. Method and apparatus for assigning network addresses based on connection authentication
US6901395B2 (en) * 2001-11-05 2005-05-31 Qualcomm Incorporated Method and apparatus for preferred roaming list compression
US8001279B2 (en) * 2001-12-21 2011-08-16 International Business Machines Corporation Method of synchronizing firewalls in a communication system based upon a server farm
US20030133554A1 (en) * 2002-01-11 2003-07-17 Nokia Corporation System and method for facilitating access to network based services
WO2003077572A1 (en) * 2002-03-13 2003-09-18 Adjungo Networks Ltd. Accessing cellular networks from non-native local networks
FI115940B (en) * 2002-06-10 2005-08-15 First Hop Oy Method and apparatus for implementing service quality in data transmissions
US7143435B1 (en) * 2002-07-31 2006-11-28 Cisco Technology, Inc. Method and apparatus for registering auto-configured network addresses based on connection authentication
US7703103B2 (en) * 2002-12-02 2010-04-20 Borland Software Corporation Serving concurrent TCP/IP connections of multiple virtual internet users with a single thread
AU2003297118A1 (en) * 2002-12-16 2004-07-29 Scientia Technologies, Inc. Apparatus and methods for communication among devices
US7274943B2 (en) * 2003-01-31 2007-09-25 Nokia Corporation Service subscription in a communication system
US7370212B2 (en) 2003-02-25 2008-05-06 Microsoft Corporation Issuing a publisher use license off-line in a digital rights management (DRM) system
FR2852759B1 (en) * 2003-03-20 2005-06-17 Bouygues Telecom Sa SMS ROUTING SYSTEM
US8521889B2 (en) * 2003-05-15 2013-08-27 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for modifying bandwidth and/or quality of service for a user session in a network
US7305230B2 (en) * 2003-07-01 2007-12-04 Nokia Corporation System, apparatus, and method for providing a mobile server
US7203967B2 (en) * 2003-09-10 2007-04-10 Qualcomm Incorporated Methods and apparatus for content protection in a wireless network
US8214536B2 (en) * 2003-09-16 2012-07-03 Research In Motion Limited Methods and apparatus for selecting a wireless network based on quality of service (QoS) criteria associated with an application
US7840646B2 (en) * 2003-10-08 2010-11-23 Yahoo! Inc. Learned upload time estimate module
US7899918B1 (en) * 2003-10-10 2011-03-01 Cisco Technology, Inc. Service accounting in a network
US7721104B2 (en) * 2003-10-20 2010-05-18 Nokia Corporation System, method and computer program product for downloading pushed content
US7797529B2 (en) * 2003-11-10 2010-09-14 Yahoo! Inc. Upload security scheme
JP2005222261A (en) * 2004-02-05 2005-08-18 Nec Corp In-train network connection service operation method, communication system using the method, and service operation system
FR2868645B1 (en) * 2004-03-30 2006-06-23 Thales Sa DYNAMIC IP NETWORK CONTROL SYSTEM
US8370917B1 (en) 2004-04-23 2013-02-05 Rockstar Consortium Us Lp Security bridging
US20060242406A1 (en) * 2005-04-22 2006-10-26 Microsoft Corporation Protected computing environment
US8347078B2 (en) * 2004-10-18 2013-01-01 Microsoft Corporation Device certificate individualization
US20060089917A1 (en) * 2004-10-22 2006-04-27 Microsoft Corporation License synchronization
US8176564B2 (en) * 2004-11-15 2012-05-08 Microsoft Corporation Special PC mode entered upon detection of undesired state
US8336085B2 (en) 2004-11-15 2012-12-18 Microsoft Corporation Tuning product policy using observed evidence of customer behavior
US20060106920A1 (en) * 2004-11-15 2006-05-18 Microsoft Corporation Method and apparatus for dynamically activating/deactivating an operating system
US8464348B2 (en) * 2004-11-15 2013-06-11 Microsoft Corporation Isolated computing environment anchored into CPU and motherboard
JP2006155373A (en) * 2004-11-30 2006-06-15 Ntt Docomo Inc Site information providing device and site information providing method
FI20041652A0 (en) * 2004-12-22 2004-12-22 Nokia Corp Default subscriber profile of the visited terminal in a packet data based mobile network
US8438645B2 (en) 2005-04-27 2013-05-07 Microsoft Corporation Secure clock with grace periods
US8725646B2 (en) 2005-04-15 2014-05-13 Microsoft Corporation Output protection levels
CA2604489C (en) * 2005-04-18 2013-11-19 Research In Motion Limited System and method for generating a wireless application from a web service definition
US9363481B2 (en) 2005-04-22 2016-06-07 Microsoft Technology Licensing, Llc Protected media pipeline
US9436804B2 (en) * 2005-04-22 2016-09-06 Microsoft Technology Licensing, Llc Establishing a unique session key using a hardware functionality scan
US20060265758A1 (en) 2005-05-20 2006-11-23 Microsoft Corporation Extensible media rights
US7734737B2 (en) * 2005-05-26 2010-06-08 Nokia Corporation Device management with configuration information
CN101213801B (en) * 2005-05-27 2012-12-12 诺基亚公司 Expanded signalling capability for network element, user equipment and system
US8353046B2 (en) * 2005-06-08 2013-01-08 Microsoft Corporation System and method for delivery of a modular operating system
US20060294204A1 (en) * 2005-06-28 2006-12-28 Kotzin Michael D Methods and devices for redirecting subscriber communication
US7675854B2 (en) 2006-02-21 2010-03-09 A10 Networks, Inc. System and method for an adaptive TCP SYN cookie with time validation
CN100466572C (en) * 2006-02-22 2009-03-04 华为技术有限公司 Equal access and initial route filtering method for packet network
US8315246B2 (en) * 2006-05-18 2012-11-20 Cisco Technology, Inc. System and method employing strategic communications between a network controller and a security gateway
US8312507B2 (en) 2006-10-17 2012-11-13 A10 Networks, Inc. System and method to apply network traffic policy to an application session
US8584199B1 (en) 2006-10-17 2013-11-12 A10 Networks, Inc. System and method to apply a packet routing policy to an application session
US20080153482A1 (en) * 2006-12-22 2008-06-26 Telefonaktiebolaget Lm Ericsson (Publ) Seamless services to a roaming user equipment
US20080184026A1 (en) * 2007-01-29 2008-07-31 Hall Martin H Metered Personal Computer Lifecycle
US20080242315A1 (en) * 2007-03-27 2008-10-02 Gm Global Technology Operations, Inc. Traffic data collection utilizing a cellular communication network and probe units
US20090131022A1 (en) * 2007-08-16 2009-05-21 Research In Motion Limited Apparatuses and Methods for Anonymous Messaging
WO2009085011A1 (en) * 2007-12-28 2009-07-09 St Electronics (Info-Comm Systems) Pte Ltd Radio gateway network
US8526616B2 (en) * 2008-03-18 2013-09-03 Christopher V. FEUDO Method for payload encryption of digital voice or data communications
US7882246B2 (en) * 2008-04-07 2011-02-01 Lg Electronics Inc. Method for updating connection profile in content delivery service
US8213904B2 (en) * 2008-05-06 2012-07-03 Motorola Mobility, Inc. Method and apparatus for provisioning an electronic communication device via a mobile internet protocol registration
US8028089B2 (en) * 2008-08-12 2011-09-27 Disney Enterprises, Inc., A Delaware Corporation On-deck detection for a web site
US8359031B2 (en) 2008-09-19 2013-01-22 Clear Channel Management Services, Inc. Computer based method and system for logging in a user mobile device at a server computer system
US9973875B2 (en) 2008-09-19 2018-05-15 Iheartmedia Management Services, Inc. Computer based method and system for logging in a user mobile device at a server computer system
US8590037B2 (en) * 2008-12-23 2013-11-19 Sandisk Technologies Inc. Managing host application privileges
US9960967B2 (en) 2009-10-21 2018-05-01 A10 Networks, Inc. Determining an application delivery server based on geo-location information
US8982893B2 (en) * 2010-03-04 2015-03-17 Telefonaktiebolaget L M Ericsson (Publ) System and method of quality of service enablement for over the top applications in a telecommunications system
CN101808138B (en) * 2010-03-31 2014-04-09 中兴通讯股份有限公司 System and method for improving service subscribing or unsubscribing speed of wireless application protocol (WAP) roaming subscriber
US8688806B2 (en) 2010-06-11 2014-04-01 Tellabs Operations, Inc. Procedure, apparatus, system, and computer program for collecting data used for analytics
US8910259B2 (en) 2010-08-14 2014-12-09 The Nielsen Company (Us), Llc Systems, methods, and apparatus to monitor mobile internet activity
US8886773B2 (en) 2010-08-14 2014-11-11 The Nielsen Company (Us), Llc Systems, methods, and apparatus to monitor mobile internet activity
US9215275B2 (en) 2010-09-30 2015-12-15 A10 Networks, Inc. System and method to balance servers based on server load status
US9609052B2 (en) 2010-12-02 2017-03-28 A10 Networks, Inc. Distributing application traffic to servers based on dynamic service response time
KR20120100376A (en) * 2011-03-04 2012-09-12 삼성에스디에스 주식회사 System and method for communication of sip messages
US9124920B2 (en) 2011-06-29 2015-09-01 The Nielson Company (Us), Llc Methods, apparatus, and articles of manufacture to identify media presentation devices
US8594617B2 (en) 2011-06-30 2013-11-26 The Nielsen Company (Us), Llc Systems, methods, and apparatus to monitor mobile internet activity
DE102011107323A1 (en) * 2011-07-06 2013-01-10 Abb Ag Method for transmitting a process image via a gateway device
US8897154B2 (en) 2011-10-24 2014-11-25 A10 Networks, Inc. Combining stateless and stateful server load balancing
US9386088B2 (en) 2011-11-29 2016-07-05 A10 Networks, Inc. Accelerating service processing using fast path TCP
US9094364B2 (en) * 2011-12-23 2015-07-28 A10 Networks, Inc. Methods to manage services over a service gateway
US10044582B2 (en) 2012-01-28 2018-08-07 A10 Networks, Inc. Generating secure name records
US8782221B2 (en) 2012-07-05 2014-07-15 A10 Networks, Inc. Method to allocate buffer for TCP proxy session based on dynamic network conditions
US9843484B2 (en) 2012-09-25 2017-12-12 A10 Networks, Inc. Graceful scaling in software driven networks
US10002141B2 (en) 2012-09-25 2018-06-19 A10 Networks, Inc. Distributed database in software driven networks
US9106561B2 (en) 2012-12-06 2015-08-11 A10 Networks, Inc. Configuration of a virtual service network
CN108027805B (en) 2012-09-25 2021-12-21 A10网络股份有限公司 Load distribution in a data network
US10021174B2 (en) 2012-09-25 2018-07-10 A10 Networks, Inc. Distributing service sessions
US9338225B2 (en) 2012-12-06 2016-05-10 A10 Networks, Inc. Forwarding policies on a virtual service network
US9531846B2 (en) 2013-01-23 2016-12-27 A10 Networks, Inc. Reducing buffer usage for TCP proxy session based on delayed acknowledgement
US9900252B2 (en) 2013-03-08 2018-02-20 A10 Networks, Inc. Application delivery controller and global server load balancer
WO2014144837A1 (en) 2013-03-15 2014-09-18 A10 Networks, Inc. Processing data packets using a policy based network path
US9301173B2 (en) 2013-03-15 2016-03-29 The Nielsen Company (Us), Llc Methods and apparatus to credit internet usage
US10356579B2 (en) 2013-03-15 2019-07-16 The Nielsen Company (Us), Llc Methods and apparatus to credit usage of mobile devices
US10027761B2 (en) 2013-05-03 2018-07-17 A10 Networks, Inc. Facilitating a secure 3 party network session by a network device
WO2014179753A2 (en) 2013-05-03 2014-11-06 A10 Networks, Inc. Facilitating secure network traffic by an application delivery controller
US10230770B2 (en) 2013-12-02 2019-03-12 A10 Networks, Inc. Network proxy layer for policy-based application proxies
US10284425B2 (en) * 2014-01-29 2019-05-07 Cellco Partnership Device registration awareness for over-the-air updates
US10020979B1 (en) 2014-03-25 2018-07-10 A10 Networks, Inc. Allocating resources in multi-core computing environments
US9942152B2 (en) 2014-03-25 2018-04-10 A10 Networks, Inc. Forwarding data packets using a service-based forwarding policy
US9942162B2 (en) 2014-03-31 2018-04-10 A10 Networks, Inc. Active application response delay time
US9806943B2 (en) 2014-04-24 2017-10-31 A10 Networks, Inc. Enabling planned upgrade/downgrade of network devices without impacting network sessions
US9906422B2 (en) 2014-05-16 2018-02-27 A10 Networks, Inc. Distributed system to determine a server's health
US10129122B2 (en) 2014-06-03 2018-11-13 A10 Networks, Inc. User defined objects for network devices
US9992229B2 (en) 2014-06-03 2018-06-05 A10 Networks, Inc. Programming a data network device using user defined scripts with licenses
US9986061B2 (en) 2014-06-03 2018-05-29 A10 Networks, Inc. Programming a data network device using user defined scripts
US10510099B2 (en) * 2014-09-10 2019-12-17 At&T Mobility Ii Llc Method and apparatus for providing content in a communication system
US9762688B2 (en) 2014-10-31 2017-09-12 The Nielsen Company (Us), Llc Methods and apparatus to improve usage crediting in mobile devices
US11423420B2 (en) 2015-02-06 2022-08-23 The Nielsen Company (Us), Llc Methods and apparatus to credit media presentations for online media distributions
US9730112B2 (en) * 2015-03-31 2017-08-08 Northrop Grumman Systems Corporation Identity based access and performance allocation
US10581976B2 (en) 2015-08-12 2020-03-03 A10 Networks, Inc. Transmission control of protocol state exchange for dynamic stateful service insertion
US10243791B2 (en) 2015-08-13 2019-03-26 A10 Networks, Inc. Automated adjustment of subscriber policies
SG10201507834SA (en) * 2015-09-21 2017-04-27 Yokogawa Electric Corp Mobile based on collaborative and interactive operations with smart mobile devices
US10318288B2 (en) 2016-01-13 2019-06-11 A10 Networks, Inc. System and method to process a chain of network applications
US10389835B2 (en) 2017-01-10 2019-08-20 A10 Networks, Inc. Application aware systems and methods to process user loadable network applications
US11848964B2 (en) * 2021-01-26 2023-12-19 Raytheon Company Zero trust end point network security device

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6134432A (en) * 1997-06-17 2000-10-17 Bulletin.Net, Inc. System and process for allowing wireless messaging
US6731945B2 (en) * 2000-01-12 2004-05-04 Telefonaktiebolaget Lm Ericsson (Publ) Private wireless WAP system
US6781960B1 (en) * 2000-02-16 2004-08-24 Telefonaktiebolaget Lm Ericsson (Publ) Wireless multi-point communication system having automatically-updated sector-based routing capabilities

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6134432A (en) * 1997-06-17 2000-10-17 Bulletin.Net, Inc. System and process for allowing wireless messaging
US6731945B2 (en) * 2000-01-12 2004-05-04 Telefonaktiebolaget Lm Ericsson (Publ) Private wireless WAP system
US6781960B1 (en) * 2000-02-16 2004-08-24 Telefonaktiebolaget Lm Ericsson (Publ) Wireless multi-point communication system having automatically-updated sector-based routing capabilities

Non-Patent Citations (14)

* Cited by examiner, † Cited by third party
Title
"Exalink Licenses Certicom's WTLS PLus & SSL Plus to Enable Secure WAP Gateway for M-Commerce Solutions"; http://www.certicom.com/about/pr/00/000509-1.html; pp. 1-3.
"Exalink to WAP-ify Comverse Backbone for $480 M"; http://www.ucalert.com/2000<SUB>-</SUB>issues/0700-04.html; pp. 3-4.
"Internet Protocol"; IETF RFC-791; Sep. 1981; http://ftp.isi.edu/in-notes/rfc791.txt; pp. 1-46.
"WAP Architecture Specification"; version Apr. 30, 1998; Wireless Application Protocol Forum, Ltd.; 1998.
"WAP Architecture Specification"; version Oct. 17, 2000; Wireless Application Protocol Forum, Ltd., 2000-2001.
"WAP TLS Profile and Tunneling Specification", prototype Apr. 11, 2001; Wireless Application Protocol Forum, Ltd. 2001.
"WAP Wireless Datagram Protocol Specification"; version Feb. 19, 2000; Wireless Application Protocol Forum Ltd. 2000; pp. 23-50.
"WAP Wireless Session Protocol Specification", version May 4, 2000; Wireless Application Protocol Forum Ltd. 2000; pp. 63-70.
"WAP Wireless Transaction Protocol Specification", version Feb. 19, 2000, Wireless Application Protocol Forum 2000; pp. 22-66.
"WAP Wireless Transport Layer Security Specification"; version Feb. 18, 2000; Wireless Application Forum, Ltd. 2000.
"Wireless Application Protocol (WAP) Specification"; version 1.2.1, Jun. 2000, WAP Forum; http://www.wapforum.com/what/technical.htm; pp. 1-5.
J. Postel; "User Datagram Protocol"; IETF RFC-768; Aug. 28, 1980; http://ftp.isi.edu/in-notes/rfc768.txt' pp. 1-3.
Open Service Architecture, Application Programming Interface-Part 1 (Release 1999); 3GPP TS 29.198 v 3.2.0, 3<SUP>rd </SUP>Generation Partnership Project; Dec. 2000.
R. Fielding, et al. "Hypertext Transfer Protocol-HTTP/1.1"; IETF RFC-2068; The Internet Society 1999.

Cited By (392)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8073477B2 (en) * 2000-04-11 2011-12-06 Telecommunication Systems, Inc. Short message distribution center
US9398108B2 (en) 2000-04-11 2016-07-19 Telecommunication Systems, Inc. Intelligent delivery agent for short message distribution center
US20110085531A1 (en) * 2000-04-11 2011-04-14 Smith Richard A Intellegent delivery agent for short message distribution center
US8542660B2 (en) 2000-04-11 2013-09-24 Telecommunication Systems, Inc. Intelligent delivery agent for short message distribution center
US9392426B2 (en) 2000-04-11 2016-07-12 Telecommunication Systems, Inc. Intelligent delivery agent for short message distribution center
US9204270B2 (en) 2000-04-11 2015-12-01 Telecommunication Systems, Inc. Intelligent delivery agent for short message distribution center
US9143908B2 (en) 2000-04-11 2015-09-22 Telecommunication Systems, Inc. Intelligent delivery agent for short message distribution center
US20110047225A1 (en) * 2000-04-11 2011-02-24 Smith Richard A Short message distribution center
US8923264B2 (en) 2000-04-11 2014-12-30 Telecommunication Systems, Inc. Intelligent delivery agent for short message distribution center
US8918520B2 (en) 2001-03-02 2014-12-23 At&T Intellectual Property I, L.P. Methods and systems for electronic data exchange utilizing centralized management technology
US8751647B1 (en) 2001-06-30 2014-06-10 Extreme Networks Method and apparatus for network login authorization
US20030095555A1 (en) * 2001-11-16 2003-05-22 Mcnamara Justin System for the validation and routing of messages
US8660537B2 (en) 2001-11-16 2014-02-25 At&T Mobility Ii Llc System for the storage and retrieval of messages
US7793334B2 (en) 2001-11-16 2010-09-07 At&T Mobility Ii Llc System and method for password protecting a distribution list
US7831240B2 (en) * 2001-11-16 2010-11-09 At&T Mobility Ii Llc System for the centralized storage of wireless customer information
US8280353B2 (en) * 2001-11-16 2012-10-02 At&T Intellectual Property I, Lp System for the centralized storage of wireless customer information
US8078761B2 (en) * 2001-11-16 2011-12-13 At&T Mobility Ii, Llc Methods and systems for routing messages through a communications network based on message content
US20110092153A1 (en) * 2001-11-16 2011-04-21 David Patron System for the Centralized Storage of Wireless Customer Information
US9436749B2 (en) 2001-11-16 2016-09-06 At&T Intellectual Property I, L.P. System for the centralized storage of wireless customer information
US20090157754A1 (en) * 2001-11-16 2009-06-18 David Patron System for the Centralized Storage of Wireless Customer Information
US20090225977A1 (en) * 2001-11-16 2009-09-10 Cardina Donald M Methods and Systems for Routing Messages Through a Communications Network Based on Message Content
US20030131311A1 (en) * 2001-11-16 2003-07-10 Mcnamara Justin Methods and systems for tracking and playing back errors in a communications network
US20030187996A1 (en) * 2001-11-16 2003-10-02 Cardina Donald M. Methods and systems for routing messages through a communications network based on message content
US20050091377A1 (en) * 2001-11-30 2005-04-28 Ralph Behrens Browser-enabled communication system and client and server for one such communication system
US7519688B2 (en) * 2001-11-30 2009-04-14 Harman Becker Automotive Systems Gmbh Browser enabled wireless communication system having encoded parameters for transmission
US20030105873A1 (en) * 2001-11-30 2003-06-05 Oracle Corporation Servicing requests that are issued in a protocol other than the protocol expected by the service
US8285880B2 (en) * 2001-11-30 2012-10-09 Oracle International Corporation Servicing requests that are issued in a protocol other than the protocol expected by the service
US20060106932A9 (en) * 2001-11-30 2006-05-18 Ralph Behrens Browser enabled communication system
US7701969B2 (en) * 2002-05-13 2010-04-20 Markport Limited Control of PLMN messaging services in IP domains
US20050117602A1 (en) * 2002-05-13 2005-06-02 Michael Carrigan Control of PLMN messaging services in IP domains
US7801976B2 (en) * 2002-05-28 2010-09-21 At&T Intellectual Property I, L.P. Service-oriented architecture systems and methods
US20040093381A1 (en) * 2002-05-28 2004-05-13 Hodges Donna Kay Service-oriented architecture systems and methods
US8837324B2 (en) 2002-06-07 2014-09-16 At&T Intellectual Property Ii, L.P. Methods for accessing end-to-end broadband network via network access server platform
US20110013620A1 (en) * 2002-06-07 2011-01-20 Chow Albert T System for Accessing End-to-End Broadband Network Via Network Access Server Platform
US7792053B1 (en) 2002-07-08 2010-09-07 At&T Intellectual Property Ii, L.P. System for accessing end-to-end broadband network via network access server platform
US7796538B1 (en) * 2002-07-08 2010-09-14 At&T Intellectual Property Ii, L.P. System for accessing end-to-end broadband network via network access server platform
US20040024894A1 (en) * 2002-08-02 2004-02-05 Osman Fazil Ismet High data rate stateful protocol processing
US8015303B2 (en) 2002-08-02 2011-09-06 Astute Networks Inc. High data rate stateful protocol processing
US8151278B1 (en) 2002-10-17 2012-04-03 Astute Networks, Inc. System and method for timer management in a stateful protocol processing system
US7814218B1 (en) 2002-10-17 2010-10-12 Astute Networks, Inc. Multi-protocol and multi-format stateful processing
US7802001B1 (en) * 2002-10-18 2010-09-21 Astute Networks, Inc. System and method for flow control within a stateful protocol processing system
US20040083296A1 (en) * 2002-10-25 2004-04-29 Metral Max E. Apparatus and method for controlling user access
US8396075B2 (en) 2002-12-02 2013-03-12 Redknee Inc. Method for implementing an open charging (OC) middleware platform and gateway system
US7802234B2 (en) 2003-01-02 2010-09-21 Oracle International Corporation Integration of context-sensitive runtime metrics into integrated development environments
US20070168913A1 (en) * 2003-01-02 2007-07-19 Sekhar Sarukkai Integration of context-sensitive run-time metrics into integrated development environments
US20040148384A1 (en) * 2003-01-23 2004-07-29 Karthik Ramakrishnan Method for implementing an internet protocol (IP) charging and rating middleware platform and gateway system
US20100067537A1 (en) * 2003-01-23 2010-03-18 Redknee Inc. Method for implementing an internet protocol (ip) charging and rating middleware platform and gateway system
US20090133114A1 (en) * 2003-01-23 2009-05-21 Redknee Inc. Method for implementing an internet protocol (ip) charging and rating middleware platform and gateway system
US8244859B2 (en) * 2003-01-23 2012-08-14 Redknee, Inc. Method for implementing an internet protocol (IP) charging and rating middleware platform and gateway system
US20120327767A1 (en) * 2003-01-23 2012-12-27 Redknee Inc. Method for implementing an internet protocol (ip) charging and rating middleware platform and gateway system
US7644158B2 (en) * 2003-01-23 2010-01-05 Redknee Inc. Method for implementing an internet protocol (IP) charging and rating middleware platform and gateway system
US7457865B2 (en) * 2003-01-23 2008-11-25 Redknee Inc. Method for implementing an internet protocol (IP) charging and rating middleware platform and gateway system
US20040199648A1 (en) * 2003-04-01 2004-10-07 Art Shelest Network zones
US9003048B2 (en) * 2003-04-01 2015-04-07 Microsoft Technology Licensing, Llc Network zones
US8874743B1 (en) * 2003-05-06 2014-10-28 Juniper Networks, Inc. Systems and methods for implementing dynamic subscriber interfaces
US7440441B2 (en) 2003-06-16 2008-10-21 Redknee Inc. Method and system for Multimedia Messaging Service (MMS) rating and billing
US8027334B2 (en) 2003-06-16 2011-09-27 Redknee, Inc. Method and system for multimedia messaging service (MMS) rating and billing
US8542676B2 (en) 2003-06-16 2013-09-24 Redknee Inc. Method and system for multimedia messaging service (MMS) rating and billing
US20040252657A1 (en) * 2003-06-16 2004-12-16 Shailesh Lakhani Method and system for multimedia messaging service (MMS) rating and billing
US20110078060A1 (en) * 2003-06-19 2011-03-31 Redknee Inc. Method for implementing a wireless local area network (wlan) gateway system
US8331902B2 (en) 2003-06-19 2012-12-11 Redknee Inc. Method for implementing a wireless local area network (WLAN) gateway system
US7873347B2 (en) 2003-06-19 2011-01-18 Redknee Inc. Method for implementing a Wireless Local Area Network (WLAN) gateway system
US20040258031A1 (en) * 2003-06-19 2004-12-23 Zabawskyj Bohdan Konstantyn Method for implemening a Wireless Local Area Network (WLAN) gateway system
US7757268B2 (en) * 2003-07-25 2010-07-13 Oracle International Corporation Policy based service management
US20070124797A1 (en) * 2003-07-25 2007-05-31 Rajiv Gupta Policy based service management
US7568107B1 (en) * 2003-08-20 2009-07-28 Extreme Networks, Inc. Method and system for auto discovery of authenticator for network login
US20080316939A1 (en) * 2003-12-26 2008-12-25 Vodafone K.K. Presence Display System and Gateway Apparatus
US7969993B2 (en) * 2003-12-26 2011-06-28 Vodafone Group Plc Presence display system and gateway apparatus
US8107472B1 (en) 2004-01-30 2012-01-31 Juniper Networks, Inc. Network single entry point for subscriber management
US7464148B1 (en) * 2004-01-30 2008-12-09 Juniper Networks, Inc. Network single entry point for subscriber management
US20050204035A1 (en) * 2004-03-12 2005-09-15 Dan Kalish System and method for identifying content service within content server
US7873705B2 (en) * 2004-03-12 2011-01-18 Flash Networks Ltd. System and method for identifying content service within content server
US20100205335A1 (en) * 2004-04-20 2010-08-12 Lexar Media Inc. Direct secondary device interface by a host
US8090886B2 (en) * 2004-04-20 2012-01-03 Micron Technology, Inc. Direct secondary device interface by a host
US8316165B2 (en) 2004-04-20 2012-11-20 Micron Technology, Inc. Direct secondary device interface by a host
US20060075014A1 (en) * 2004-09-29 2006-04-06 Intel Corporation Method and apparatus for securing devices in a network
US8179870B2 (en) * 2004-09-29 2012-05-15 Intel Corporation Method and apparatus for securing devices in a network
US20120210132A1 (en) * 2004-09-29 2012-08-16 Tharappel Francis M Method and apparatus for securing devices in a network
US8542662B2 (en) * 2004-09-29 2013-09-24 Intel Corporation Method and apparatus for securing devices in a network
US8161278B2 (en) 2005-03-15 2012-04-17 Trapeze Networks, Inc. System and method for distributing keys in a wireless network
US8635444B2 (en) 2005-03-15 2014-01-21 Trapeze Networks, Inc. System and method for distributing keys in a wireless network
US7870265B2 (en) 2005-06-30 2011-01-11 Oracle International Corporation System and method for managing communications sessions in a network
US20070005770A1 (en) * 2005-06-30 2007-01-04 Bea Systems, Inc. System and method for managing communications sessions in a network
US8514827B2 (en) 2005-10-13 2013-08-20 Trapeze Networks, Inc. System and network for wireless network monitoring
US8218449B2 (en) 2005-10-13 2012-07-10 Trapeze Networks, Inc. System and method for remote monitoring in a wireless network
US8116275B2 (en) 2005-10-13 2012-02-14 Trapeze Networks, Inc. System and network for wireless network monitoring
US8638762B2 (en) 2005-10-13 2014-01-28 Trapeze Networks, Inc. System and method for network integrity
US8457031B2 (en) 2005-10-13 2013-06-04 Trapeze Networks, Inc. System and method for reliable multicast
US20070106800A1 (en) * 2005-11-04 2007-05-10 Bea Systems, Inc. System and method for controlling access to legacy push protocols based upon a policy
US20070104208A1 (en) * 2005-11-04 2007-05-10 Bea Systems, Inc. System and method for shaping traffic
US20070104186A1 (en) * 2005-11-04 2007-05-10 Bea Systems, Inc. System and method for a gatekeeper in a communications network
US7957403B2 (en) 2005-11-04 2011-06-07 Oracle International Corporation System and method for controlling access to legacy multimedia message protocols based upon a policy
US7788386B2 (en) 2005-11-04 2010-08-31 Bea Systems, Inc. System and method for shaping traffic
US7953877B2 (en) 2005-11-04 2011-05-31 Oracle International Corporation System and method for controlling data flow based upon a temporal policy
US8626934B2 (en) * 2005-11-04 2014-01-07 Oracle International Corporation System and method for controlling access to legacy push protocols based upon a policy
US20070106801A1 (en) * 2005-11-04 2007-05-10 Bea Systems, Inc. System and method for controlling access to legacy short message peer-to-peer protocols based upon a policy
US20070106808A1 (en) * 2005-11-04 2007-05-10 Bea Systems, Inc. System and method for controlling data flow based upon a temporal policy
US20070133574A1 (en) * 2005-12-01 2007-06-14 Tekelec Methods, systems, and computer program products for using an E.164 number (ENUM) database for message service message routing resolution among 2G and subsequent generation network systems
US7889716B2 (en) * 2005-12-01 2011-02-15 Tekelec Methods, systems, and computer program products for using an E.164 number (ENUM) database for message service message routing resolution among 2G and subsequent generation network systems
US20070208860A1 (en) * 2006-03-02 2007-09-06 Zellner Samuel N User specific data collection
US20110312300A1 (en) * 2006-03-02 2011-12-22 Andrew Silver Mobile application gateway for connecting devices on a cellular network with individual enterprise and data networks
US11849380B2 (en) 2006-03-02 2023-12-19 Tango Networks, Inc. Call flow system and method for use in a VoIP telecommunication system
US11871216B2 (en) 2006-03-02 2024-01-09 Tango Networks, Inc. Call flow system and method for use in a legacy telecommunication system
US11811554B2 (en) * 2006-03-02 2023-11-07 Tango Networks, Inc. Mobile application gateway for connecting devices on a cellular network with individual enterprise and data networks
US8233890B2 (en) * 2006-03-02 2012-07-31 At&T Intellectual Property I, L.P. Environment independent user preference communication
US11405846B2 (en) 2006-03-02 2022-08-02 Tango Networks, Inc. Call flow system and method for use in a legacy telecommunication system
US8861491B2 (en) * 2006-03-02 2014-10-14 Tango Networks, Inc. Mobile application gateway for connecting devices on a cellular network with individual enterprise and data networks
US20150031331A1 (en) * 2006-03-02 2015-01-29 Tango Networks, Inc. Mobile application gateway for connecting devices on a cellular network with individual enterprise and data networks
US11638126B2 (en) 2006-03-02 2023-04-25 Tango Networks, Inc. System and method for enabling call originations using SMS and hotline capabilities
US20100223555A1 (en) * 2006-03-02 2010-09-02 At&T Intellectual Property I, L.P. Environment Independent User Preference Communication
US8526925B2 (en) 2006-03-02 2013-09-03 At&T Intellectual Property I, L.P. Environment independent user preference communication
US20070208861A1 (en) * 2006-03-02 2007-09-06 Zellner Samuel N User preference interpretation
US9622078B2 (en) * 2006-03-02 2017-04-11 Tango Networks, Inc. Mobile application gateway for connecting devices on a cellular network with individual enterprise and data networks
US8964747B2 (en) 2006-05-03 2015-02-24 Trapeze Networks, Inc. System and method for restricting network access using forwarding databases
US8112525B2 (en) 2006-05-16 2012-02-07 Oracle International Corporation Engine near cache for reducing latency in a telecommunications environment
US8001250B2 (en) 2006-05-16 2011-08-16 Oracle International Corporation SIP and HTTP convergence in network computing environments
US8171466B2 (en) 2006-05-16 2012-05-01 Oracle International Corporation Hitless application upgrade for SIP server architecture
US20080189421A1 (en) * 2006-05-16 2008-08-07 Bea Systems, Inc. SIP and HTTP Convergence in Network Computing Environments
US20090019158A1 (en) * 2006-05-16 2009-01-15 Bea Systems, Inc. Engine Near Cache for Reducing Latency in a Telecommunications Environment
US20080127232A1 (en) * 2006-05-17 2008-05-29 Bea Systems, Inc. Diameter Protocol and SH Interface Support for SIP Server Architecture
US8219697B2 (en) 2006-05-17 2012-07-10 Oracle International Corporation Diameter protocol and SH interface support for SIP server architecture
US8966018B2 (en) 2006-05-19 2015-02-24 Trapeze Networks, Inc. Automated network device configuration and network deployment
US9258702B2 (en) 2006-06-09 2016-02-09 Trapeze Networks, Inc. AP-local dynamic switching
US10327202B2 (en) 2006-06-09 2019-06-18 Trapeze Networks, Inc. AP-local dynamic switching
US10798650B2 (en) 2006-06-09 2020-10-06 Trapeze Networks, Inc. AP-local dynamic switching
US10638304B2 (en) 2006-06-09 2020-04-28 Trapeze Networks, Inc. Sharing data between wireless switches system and method
US9838942B2 (en) 2006-06-09 2017-12-05 Trapeze Networks, Inc. AP-local dynamic switching
US10834585B2 (en) 2006-06-09 2020-11-10 Trapeze Networks, Inc. Untethered access point mesh system and method
US11758398B2 (en) 2006-06-09 2023-09-12 Juniper Networks, Inc. Untethered access point mesh system and method
US11432147B2 (en) 2006-06-09 2022-08-30 Trapeze Networks, Inc. Untethered access point mesh system and method
US9191799B2 (en) 2006-06-09 2015-11-17 Juniper Networks, Inc. Sharing data between wireless switches system and method
US8818322B2 (en) 2006-06-09 2014-08-26 Trapeze Networks, Inc. Untethered access point mesh system and method
US11627461B2 (en) 2006-06-09 2023-04-11 Juniper Networks, Inc. AP-local dynamic switching
US20080027943A1 (en) * 2006-07-31 2008-01-31 Clemens Jonathan P Location-aware network access method and apparatus
US20080059635A1 (en) * 2006-08-31 2008-03-06 Redknee Inc. Policy services
US8775621B2 (en) 2006-08-31 2014-07-08 Redknee Inc. Policy services
US8340110B2 (en) * 2006-09-15 2012-12-25 Trapeze Networks, Inc. Quality of service provisioning for wireless networks
US20080155310A1 (en) * 2006-10-10 2008-06-26 Bea Systems, Inc. SIP server architecture fault tolerance and failover
US7661027B2 (en) 2006-10-10 2010-02-09 Bea Systems, Inc. SIP server architecture fault tolerance and failover
DE102006051652A1 (en) * 2006-11-02 2008-05-08 Deutsche Telekom Ag Parameters changing method for use during connection e.g. analog telephone, of participant with Internet, involves converting instructions into other instructions according to protocol, and supplying instructions to computer
US20080137832A1 (en) * 2006-12-07 2008-06-12 Tekelec Methods, systems, and computer program products for providing quality of service using E.164 number mapping (ENUM) data in a communications network
US8254551B2 (en) 2006-12-07 2012-08-28 Tekelec, Inc. Methods, systems, and computer program products for providing quality of service using E.164 number mapping (ENUM) data in a communications network
US20080147551A1 (en) * 2006-12-13 2008-06-19 Bea Systems, Inc. System and Method for a SIP Server with Online Charging
US20080147524A1 (en) * 2006-12-13 2008-06-19 Bea Systems, Inc. System and Method for a SIP Server with Offline Charging
US9667430B2 (en) 2006-12-13 2017-05-30 Oracle International Corporation System and method for a SIP server with offline charging
US8670383B2 (en) 2006-12-28 2014-03-11 Trapeze Networks, Inc. System and method for aggregation and queuing in a wireless network
US20080235361A1 (en) * 2007-03-21 2008-09-25 David Crosbie Management layer method and apparatus for dynamic assignment of users to computer resources
US7996541B2 (en) 2007-06-15 2011-08-09 Tekelec Methods, systems, and computer program products for identifying a serving home subscriber server (HSS) in a communications network
US20080311917A1 (en) * 2007-06-15 2008-12-18 Tekelec Methods, systems, and computer program products for identifying a serving home subscriber server (HSS) in a communications network
US20090019155A1 (en) * 2007-07-11 2009-01-15 Verizon Services Organization Inc. Token-based crediting of network usage
US20090019108A1 (en) * 2007-07-11 2009-01-15 International Business Machines Corporation System and method for application server/operating system network/configuration management
US9009309B2 (en) * 2007-07-11 2015-04-14 Verizon Patent And Licensing Inc. Token-based crediting of network usage
US8180865B2 (en) * 2007-07-11 2012-05-15 International Business Machines Corporation System and method for application server/operating system network/configuration management
US20090043704A1 (en) * 2007-08-10 2009-02-12 Tekelec Methods, systems, and computer program products for performing message deposit transaction screening
US8538000B2 (en) 2007-08-10 2013-09-17 Tekelec, Inc. Methods, systems, and computer program products for performing message deposit transaction screening
US8902904B2 (en) 2007-09-07 2014-12-02 Trapeze Networks, Inc. Network assignment based on priority
US20110082779A1 (en) * 2007-09-13 2011-04-07 Redknee Inc. Billing profile manager
US8238942B2 (en) 2007-11-21 2012-08-07 Trapeze Networks, Inc. Wireless station location detection
US9059871B2 (en) 2007-12-27 2015-06-16 Redknee Inc. Policy-based communication system and method
US20090227276A1 (en) * 2008-03-07 2009-09-10 Devesh Agarwal Methods, systems, and computer readable media for routing a message service message through a communications network
US8594679B2 (en) 2008-03-07 2013-11-26 Tekelec Global, Inc. Methods, systems, and computer readable media for routing a message service message through a communications network
US8150357B2 (en) 2008-03-28 2012-04-03 Trapeze Networks, Inc. Smoothing filter for irregular update intervals
US8725123B2 (en) 2008-06-05 2014-05-13 Headwater Partners I Llc Communications device with secure data path processing agents
US8924469B2 (en) 2008-06-05 2014-12-30 Headwater Partners I Llc Enterprise access control and accounting allocation for access networks
US8978105B2 (en) 2008-07-25 2015-03-10 Trapeze Networks, Inc. Affirming network relationships and resource access via related networks
US8238298B2 (en) 2008-08-29 2012-08-07 Trapeze Networks, Inc. Picking an optimal channel for an access point in a wireless network
US9584959B2 (en) 2008-11-24 2017-02-28 Tekelec Global, Inc. Systems, methods, and computer readable media for location-sensitive called-party number translation in a telecommunications network
US9578182B2 (en) 2009-01-28 2017-02-21 Headwater Partners I Llc Mobile device and service management
US9647918B2 (en) 2009-01-28 2017-05-09 Headwater Research Llc Mobile device and method attributing media services network usage to requesting application
US8737957B2 (en) 2009-01-28 2014-05-27 Headwater Partners I Llc Automated device provisioning and activation
US8745191B2 (en) 2009-01-28 2014-06-03 Headwater Partners I Llc System and method for providing user notifications
US8745220B2 (en) 2009-01-28 2014-06-03 Headwater Partners I Llc System and method for providing user notifications
US11923995B2 (en) 2009-01-28 2024-03-05 Headwater Research Llc Device-assisted services for protecting network capacity
US8634821B2 (en) 2009-01-28 2014-01-21 Headwater Partners I Llc Device assisted services install
US8635678B2 (en) 2009-01-28 2014-01-21 Headwater Partners I Llc Automated device provisioning and activation
US8788661B2 (en) 2009-01-28 2014-07-22 Headwater Partners I Llc Device assisted CDR creation, aggregation, mediation and billing
US8793758B2 (en) 2009-01-28 2014-07-29 Headwater Partners I Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US8797908B2 (en) 2009-01-28 2014-08-05 Headwater Partners I Llc Automated device provisioning and activation
US8799451B2 (en) 2009-01-28 2014-08-05 Headwater Partners I Llc Verifiable service policy implementation for intermediate networking devices
US8634805B2 (en) 2009-01-28 2014-01-21 Headwater Partners I Llc Device assisted CDR creation aggregation, mediation and billing
US8639811B2 (en) 2009-01-28 2014-01-28 Headwater Partners I Llc Automated device provisioning and activation
US11757943B2 (en) 2009-01-28 2023-09-12 Headwater Research Llc Automated device provisioning and activation
US8839387B2 (en) 2009-01-28 2014-09-16 Headwater Partners I Llc Roaming services network and overlay networks
US8839388B2 (en) 2009-01-28 2014-09-16 Headwater Partners I Llc Automated device provisioning and activation
US8630630B2 (en) 2009-01-28 2014-01-14 Headwater Partners I Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US11750477B2 (en) 2009-01-28 2023-09-05 Headwater Research Llc Adaptive ambient services
US8630617B2 (en) 2009-01-28 2014-01-14 Headwater Partners I Llc Device group partitions and settlement platform
US8868455B2 (en) 2009-01-28 2014-10-21 Headwater Partners I Llc Adaptive ambient services
US8630611B2 (en) 2009-01-28 2014-01-14 Headwater Partners I Llc Automated device provisioning and activation
US8886162B2 (en) 2009-01-28 2014-11-11 Headwater Partners I Llc Restricting end-user device communications over a wireless access network associated with a cost
US8893009B2 (en) 2009-01-28 2014-11-18 Headwater Partners I Llc End user device that secures an association of application to service policy with an application certificate check
US8898079B2 (en) 2009-01-28 2014-11-25 Headwater Partners I Llc Network based ambient services
US8897744B2 (en) * 2009-01-28 2014-11-25 Headwater Partners I Llc Device assisted ambient services
US8897743B2 (en) 2009-01-28 2014-11-25 Headwater Partners I Llc Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account
US8898293B2 (en) 2009-01-28 2014-11-25 Headwater Partners I Llc Service offer set publishing to device agent with on-device service selection
US8631102B2 (en) 2009-01-28 2014-01-14 Headwater Partners I Llc Automated device provisioning and activation
US8903452B2 (en) * 2009-01-28 2014-12-02 Headwater Partners I Llc Device assisted ambient services
US8630192B2 (en) 2009-01-28 2014-01-14 Headwater Partners I Llc Verifiable and accurate service usage monitoring for intermediate networking devices
US8924549B2 (en) 2009-01-28 2014-12-30 Headwater Partners I Llc Network based ambient services
US8626115B2 (en) 2009-01-28 2014-01-07 Headwater Partners I Llc Wireless network service interfaces
US8924543B2 (en) 2009-01-28 2014-12-30 Headwater Partners I Llc Service design center for device assisted services
US8713630B2 (en) 2009-01-28 2014-04-29 Headwater Partners I Llc Verifiable service policy implementation for intermediate networking devices
US11665592B2 (en) 2009-01-28 2023-05-30 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US11665186B2 (en) 2009-01-28 2023-05-30 Headwater Research Llc Communications device with secure data path processing agents
US8948025B2 (en) 2009-01-28 2015-02-03 Headwater Partners I Llc Remotely configurable device agent for packet routing
US11589216B2 (en) 2009-01-28 2023-02-21 Headwater Research Llc Service selection set publishing to device agent with on-device service selection
US11582593B2 (en) 2009-01-28 2023-02-14 Head Water Research Llc Adapting network policies based on device service processor configuration
US8695073B2 (en) 2009-01-28 2014-04-08 Headwater Partners I Llc Automated device provisioning and activation
US11570309B2 (en) 2009-01-28 2023-01-31 Headwater Research Llc Service design center for device assisted services
US8688099B2 (en) 2009-01-28 2014-04-01 Headwater Partners I Llc Open development system for access service providers
US8589541B2 (en) 2009-01-28 2013-11-19 Headwater Partners I Llc Device-assisted services for protecting network capacity
US8588110B2 (en) 2009-01-28 2013-11-19 Headwater Partners I Llc Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account
US9014026B2 (en) 2009-01-28 2015-04-21 Headwater Partners I Llc Network based service profile management with user preference, adaptive policy, network neutrality, and user privacy
US11563592B2 (en) 2009-01-28 2023-01-24 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US9615192B2 (en) 2009-01-28 2017-04-04 Headwater Research Llc Message link server with plural message delivery triggers
US9037127B2 (en) 2009-01-28 2015-05-19 Headwater Partners I Llc Device agent for remote user configuration of wireless network access
US8675507B2 (en) 2009-01-28 2014-03-18 Headwater Partners I Llc Service profile management with user preference, adaptive policy, network neutrality and user privacy for intermediate networking devices
US9094311B2 (en) 2009-01-28 2015-07-28 Headwater Partners I, Llc Techniques for attribution of mobile device data traffic to initiating end-user application
US11538106B2 (en) 2009-01-28 2022-12-27 Headwater Research Llc Wireless end-user device providing ambient or sponsored services
US9137701B2 (en) 2009-01-28 2015-09-15 Headwater Partners I Llc Wireless end-user device with differentiated network access for background and foreground device applications
US9137739B2 (en) 2009-01-28 2015-09-15 Headwater Partners I Llc Network based service policy implementation with network neutrality and user privacy
US9143976B2 (en) 2009-01-28 2015-09-22 Headwater Partners I Llc Wireless end-user device with differentiated network access and access status for background and foreground device applications
US8583781B2 (en) 2009-01-28 2013-11-12 Headwater Partners I Llc Simplified service network architecture
US11533642B2 (en) 2009-01-28 2022-12-20 Headwater Research Llc Device group partitions and settlement platform
US9154428B2 (en) 2009-01-28 2015-10-06 Headwater Partners I Llc Wireless end-user device with differentiated network access selectively applied to different applications
US9173104B2 (en) 2009-01-28 2015-10-27 Headwater Partners I Llc Mobile device with device agents to detect a disallowed access to a requested mobile data service and guide a multi-carrier selection and activation sequence
US9179315B2 (en) 2009-01-28 2015-11-03 Headwater Partners I Llc Mobile device with data service monitoring, categorization, and display for different applications and networks
US9179316B2 (en) 2009-01-28 2015-11-03 Headwater Partners I Llc Mobile device with user controls and policy agent to control application access to device location data
US9179359B2 (en) 2009-01-28 2015-11-03 Headwater Partners I Llc Wireless end-user device with differentiated network access status for different device applications
US9179308B2 (en) 2009-01-28 2015-11-03 Headwater Partners I Llc Network tools for analysis, design, testing, and production of services
US8570908B2 (en) 2009-01-28 2013-10-29 Headwater Partners I Llc Automated device provisioning and activation
US9198117B2 (en) 2009-01-28 2015-11-24 Headwater Partners I Llc Network system with common secure wireless message service serving multiple applications on multiple wireless devices
US9198042B2 (en) 2009-01-28 2015-11-24 Headwater Partners I Llc Security techniques for device assisted services
US9198075B2 (en) 2009-01-28 2015-11-24 Headwater Partners I Llc Wireless end-user device with differential traffic control policy list applicable to one of several wireless modems
US9198074B2 (en) 2009-01-28 2015-11-24 Headwater Partners I Llc Wireless end-user device with differential traffic control policy list and applying foreground classification to roaming wireless data service
US9198076B2 (en) 2009-01-28 2015-11-24 Headwater Partners I Llc Wireless end-user device with power-control-state-based wireless network access policy for background applications
US9641957B2 (en) 2009-01-28 2017-05-02 Headwater Research Llc Automated device provisioning and activation
US8547872B2 (en) 2009-01-28 2013-10-01 Headwater Partners I Llc Verifiable and accurate service usage monitoring for intermediate networking devices
US9204282B2 (en) * 2009-01-28 2015-12-01 Headwater Partners I Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US9215159B2 (en) 2009-01-28 2015-12-15 Headwater Partners I Llc Data usage monitoring for media data services used by applications
US9215613B2 (en) 2009-01-28 2015-12-15 Headwater Partners I Llc Wireless end-user device with differential traffic control policy list having limited user control
US9220027B1 (en) 2009-01-28 2015-12-22 Headwater Partners I Llc Wireless end-user device with policy-based controls for WWAN network usage and modem state changes requested by specific applications
US9225797B2 (en) 2009-01-28 2015-12-29 Headwater Partners I Llc System for providing an adaptive wireless ambient service to a mobile device
US9232403B2 (en) 2009-01-28 2016-01-05 Headwater Partners I Llc Mobile device with common secure wireless message service serving multiple applications
US9247450B2 (en) 2009-01-28 2016-01-26 Headwater Partners I Llc Quality of service for device assisted services
US9253663B2 (en) 2009-01-28 2016-02-02 Headwater Partners I Llc Controlling mobile device communications on a roaming network based on device state
US9258735B2 (en) 2009-01-28 2016-02-09 Headwater Partners I Llc Device-assisted services for protecting network capacity
US8548428B2 (en) 2009-01-28 2013-10-01 Headwater Partners I Llc Device group partitions and settlement platform
US9270559B2 (en) 2009-01-28 2016-02-23 Headwater Partners I Llc Service policy implementation for an end-user device having a control application or a proxy agent for routing an application traffic flow
US9271184B2 (en) 2009-01-28 2016-02-23 Headwater Partners I Llc Wireless end-user device with per-application data limit and traffic control policy list limiting background application traffic
US9277445B2 (en) 2009-01-28 2016-03-01 Headwater Partners I Llc Wireless end-user device with differential traffic control policy list and applying foreground classification to wireless data service
US9277433B2 (en) 2009-01-28 2016-03-01 Headwater Partners I Llc Wireless end-user device with policy-based aggregation of network activity requested by applications
US11516301B2 (en) 2009-01-28 2022-11-29 Headwater Research Llc Enhanced curfew and protection associated with a device group
US11494837B2 (en) 2009-01-28 2022-11-08 Headwater Research Llc Virtualized policy and charging system
US9319913B2 (en) 2009-01-28 2016-04-19 Headwater Partners I Llc Wireless end-user device with secure network-provided differential traffic control policy list
US9351193B2 (en) 2009-01-28 2016-05-24 Headwater Partners I Llc Intermediate networking devices
US9386165B2 (en) 2009-01-28 2016-07-05 Headwater Partners I Llc System and method for providing user notifications
US9386121B2 (en) 2009-01-28 2016-07-05 Headwater Partners I Llc Method for providing an adaptive wireless ambient service to a mobile device
US11477246B2 (en) 2009-01-28 2022-10-18 Headwater Research Llc Network service plan design
US9392462B2 (en) 2009-01-28 2016-07-12 Headwater Partners I Llc Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy
US8527630B2 (en) * 2009-01-28 2013-09-03 Headwater Partners I Llc Adaptive ambient services
US8516552B2 (en) 2009-01-28 2013-08-20 Headwater Partners I Llc Verifiable service policy implementation for intermediate networking devices
US9491564B1 (en) 2009-01-28 2016-11-08 Headwater Partners I Llc Mobile device and method with secure network messaging for authorized components
US9491199B2 (en) 2009-01-28 2016-11-08 Headwater Partners I Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US9521578B2 (en) 2009-01-28 2016-12-13 Headwater Partners I Llc Wireless end-user device with application program interface to allow applications to access application-specific aspects of a wireless network access policy
US9532261B2 (en) 2009-01-28 2016-12-27 Headwater Partners I Llc System and method for wireless network offloading
US9532161B2 (en) 2009-01-28 2016-12-27 Headwater Partners I Llc Wireless device with application data flow tagging and network stack-implemented network access policy
US9544397B2 (en) 2009-01-28 2017-01-10 Headwater Partners I Llc Proxy server for providing an adaptive wireless ambient service to a mobile device
US9557889B2 (en) 2009-01-28 2017-01-31 Headwater Partners I Llc Service plan design, user interfaces, application programming interfaces, and device management
US9565707B2 (en) 2009-01-28 2017-02-07 Headwater Partners I Llc Wireless end-user device with wireless data attribution to multiple personas
US9565543B2 (en) 2009-01-28 2017-02-07 Headwater Partners I Llc Device group partitions and settlement platform
US9571559B2 (en) 2009-01-28 2017-02-14 Headwater Partners I Llc Enhanced curfew and protection associated with a device group
US9572019B2 (en) 2009-01-28 2017-02-14 Headwater Partners LLC Service selection set published to device agent with on-device service selection
US8640198B2 (en) 2009-01-28 2014-01-28 Headwater Partners I Llc Automated device provisioning and activation
US8635335B2 (en) 2009-01-28 2014-01-21 Headwater Partners I Llc System and method for wireless network offloading
US9591474B2 (en) 2009-01-28 2017-03-07 Headwater Partners I Llc Adapting network policies based on device service processor configuration
US9609510B2 (en) 2009-01-28 2017-03-28 Headwater Research Llc Automated credential porting for mobile devices
US9609459B2 (en) 2009-01-28 2017-03-28 Headwater Research Llc Network tools for analysis, design, testing, and production of services
US9609544B2 (en) 2009-01-28 2017-03-28 Headwater Research Llc Device-assisted services for protecting network capacity
US9026079B2 (en) 2009-01-28 2015-05-05 Headwater Partners I Llc Wireless network service interfaces
US8724554B2 (en) 2009-01-28 2014-05-13 Headwater Partners I Llc Open transaction central billing system
US9204374B2 (en) 2009-01-28 2015-12-01 Headwater Partners I Llc Multicarrier over-the-air cellular network activation server
US8639935B2 (en) 2009-01-28 2014-01-28 Headwater Partners I Llc Automated device provisioning and activation
US11425580B2 (en) 2009-01-28 2022-08-23 Headwater Research Llc System and method for wireless network offloading
US11412366B2 (en) 2009-01-28 2022-08-09 Headwater Research Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US9674731B2 (en) 2009-01-28 2017-06-06 Headwater Research Llc Wireless device applying different background data traffic policies to different device applications
US11405224B2 (en) 2009-01-28 2022-08-02 Headwater Research Llc Device-assisted services for protecting network capacity
US9705771B2 (en) 2009-01-28 2017-07-11 Headwater Partners I Llc Attribution of mobile device data traffic to end-user application based on socket flows
US9706061B2 (en) 2009-01-28 2017-07-11 Headwater Partners I Llc Service design center for device assisted services
US9749898B2 (en) 2009-01-28 2017-08-29 Headwater Research Llc Wireless end-user device with differential traffic control policy list applicable to one of several wireless modems
US9749899B2 (en) 2009-01-28 2017-08-29 Headwater Research Llc Wireless end-user device with network traffic API to indicate unavailability of roaming wireless connection to background applications
US9755842B2 (en) 2009-01-28 2017-09-05 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US9769207B2 (en) 2009-01-28 2017-09-19 Headwater Research Llc Wireless network service interfaces
US9819808B2 (en) 2009-01-28 2017-11-14 Headwater Research Llc Hierarchical service policies for creating service usage data records for a wireless end-user device
US20130109378A1 (en) * 2009-01-28 2013-05-02 Headwater Partners I Llc Enhanced roaming services and converged carrier networks with device assisted services and a proxy
US9858559B2 (en) 2009-01-28 2018-01-02 Headwater Research Llc Network service plan design
US9866642B2 (en) 2009-01-28 2018-01-09 Headwater Research Llc Wireless end-user device with wireless modem power state control policy for background applications
US9942796B2 (en) 2009-01-28 2018-04-10 Headwater Research Llc Quality of service for device assisted services
US9954975B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Enhanced curfew and protection associated with a device group
US9955332B2 (en) 2009-01-28 2018-04-24 Headwater Research Llc Method for child wireless device activation to subscriber account of a master wireless device
US9973930B2 (en) 2009-01-28 2018-05-15 Headwater Research Llc End user device that secures an association of application to service policy with an application certificate check
US9980146B2 (en) 2009-01-28 2018-05-22 Headwater Research Llc Communications device with secure data path processing agents
US10028144B2 (en) 2009-01-28 2018-07-17 Headwater Research Llc Security techniques for device assisted services
US10057141B2 (en) 2009-01-28 2018-08-21 Headwater Research Llc Proxy system and method for adaptive ambient services
US10057775B2 (en) 2009-01-28 2018-08-21 Headwater Research Llc Virtualized policy and charging system
US10064055B2 (en) 2009-01-28 2018-08-28 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US10064033B2 (en) 2009-01-28 2018-08-28 Headwater Research Llc Device group partitions and settlement platform
US10070305B2 (en) 2009-01-28 2018-09-04 Headwater Research Llc Device assisted services install
US10080250B2 (en) 2009-01-28 2018-09-18 Headwater Research Llc Enterprise access control and accounting allocation for access networks
US10165447B2 (en) 2009-01-28 2018-12-25 Headwater Research Llc Network service plan design
US8667571B2 (en) 2009-01-28 2014-03-04 Headwater Partners I Llc Automated device provisioning and activation
US10171681B2 (en) 2009-01-28 2019-01-01 Headwater Research Llc Service design center for device assisted services
US10171988B2 (en) 2009-01-28 2019-01-01 Headwater Research Llc Adapting network policies based on device service processor configuration
US10171990B2 (en) 2009-01-28 2019-01-01 Headwater Research Llc Service selection set publishing to device agent with on-device service selection
US10200541B2 (en) 2009-01-28 2019-02-05 Headwater Research Llc Wireless end-user device with divided user space/kernel space traffic policy system
US10237757B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc System and method for wireless network offloading
US10237773B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc Device-assisted services for protecting network capacity
US10237146B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc Adaptive ambient services
US10248996B2 (en) 2009-01-28 2019-04-02 Headwater Research Llc Method for operating a wireless end-user device mobile payment agent
US10264138B2 (en) 2009-01-28 2019-04-16 Headwater Research Llc Mobile device and service management
US10321320B2 (en) 2009-01-28 2019-06-11 Headwater Research Llc Wireless network buffered message system
US10320990B2 (en) 2009-01-28 2019-06-11 Headwater Research Llc Device assisted CDR creation, aggregation, mediation and billing
US10326800B2 (en) 2009-01-28 2019-06-18 Headwater Research Llc Wireless network service interfaces
US10326675B2 (en) 2009-01-28 2019-06-18 Headwater Research Llc Flow tagging for service policy implementation
US20130045710A1 (en) * 2009-01-28 2013-02-21 Headwater Partners I, Llc Device Assisted Ambient Services
US10462627B2 (en) 2009-01-28 2019-10-29 Headwater Research Llc Service plan design, user interfaces, application programming interfaces, and device management
US10492102B2 (en) 2009-01-28 2019-11-26 Headwater Research Llc Intermediate networking devices
US10536983B2 (en) 2009-01-28 2020-01-14 Headwater Research Llc Enterprise access control and accounting allocation for access networks
US10582375B2 (en) 2009-01-28 2020-03-03 Headwater Research Llc Device assisted services install
US20130040703A1 (en) * 2009-01-28 2013-02-14 Headwater Partner I, LLC Device Assisted Ambient Services
US10681179B2 (en) 2009-01-28 2020-06-09 Headwater Research Llc Enhanced curfew and protection associated with a device group
US10694385B2 (en) 2009-01-28 2020-06-23 Headwater Research Llc Security techniques for device assisted services
US10716006B2 (en) 2009-01-28 2020-07-14 Headwater Research Llc End user device that secures an association of application to service policy with an application certificate check
US10715342B2 (en) 2009-01-28 2020-07-14 Headwater Research Llc Managing service user discovery and service launch object placement on a device
US10749700B2 (en) 2009-01-28 2020-08-18 Headwater Research Llc Device-assisted services for protecting network capacity
US10771980B2 (en) 2009-01-28 2020-09-08 Headwater Research Llc Communications device with secure data path processing agents
US10779177B2 (en) 2009-01-28 2020-09-15 Headwater Research Llc Device group partitions and settlement platform
US10783581B2 (en) 2009-01-28 2020-09-22 Headwater Research Llc Wireless end-user device providing ambient or sponsored services
US10791471B2 (en) 2009-01-28 2020-09-29 Headwater Research Llc System and method for wireless network offloading
US20120317284A1 (en) * 2009-01-28 2012-12-13 Headwater Partners I Llc Adaptive Ambient Services
US10798252B2 (en) 2009-01-28 2020-10-06 Headwater Research Llc System and method for providing user notifications
US10798254B2 (en) 2009-01-28 2020-10-06 Headwater Research Llc Service design center for device assisted services
US10798558B2 (en) 2009-01-28 2020-10-06 Headwater Research Llc Adapting network policies based on device service processor configuration
US10803518B2 (en) 2009-01-28 2020-10-13 Headwater Research Llc Virtualized policy and charging system
US11405429B2 (en) 2009-01-28 2022-08-02 Headwater Research Llc Security techniques for device assisted services
US10834577B2 (en) 2009-01-28 2020-11-10 Headwater Research Llc Service offer set publishing to device agent with on-device service selection
US8666364B2 (en) 2009-01-28 2014-03-04 Headwater Partners I Llc Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account
US10841839B2 (en) 2009-01-28 2020-11-17 Headwater Research Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US10848330B2 (en) 2009-01-28 2020-11-24 Headwater Research Llc Device-assisted services for protecting network capacity
US10855559B2 (en) 2009-01-28 2020-12-01 Headwater Research Llc Adaptive ambient services
US10869199B2 (en) 2009-01-28 2020-12-15 Headwater Research Llc Network service plan design
US11363496B2 (en) 2009-01-28 2022-06-14 Headwater Research Llc Intermediate networking devices
US10985977B2 (en) 2009-01-28 2021-04-20 Headwater Research Llc Quality of service for device assisted services
US11039020B2 (en) 2009-01-28 2021-06-15 Headwater Research Llc Mobile device and service management
US11096055B2 (en) 2009-01-28 2021-08-17 Headwater Research Llc Automated device provisioning and activation
US11134102B2 (en) 2009-01-28 2021-09-28 Headwater Research Llc Verifiable device assisted service usage monitoring with reporting, synchronization, and notification
US11190645B2 (en) 2009-01-28 2021-11-30 Headwater Research Llc Device assisted CDR creation, aggregation, mediation and billing
US11190545B2 (en) 2009-01-28 2021-11-30 Headwater Research Llc Wireless network service interfaces
US11190427B2 (en) 2009-01-28 2021-11-30 Headwater Research Llc Flow tagging for service policy implementation
US11218854B2 (en) 2009-01-28 2022-01-04 Headwater Research Llc Service plan design, user interfaces, application programming interfaces, and device management
US11219074B2 (en) 2009-01-28 2022-01-04 Headwater Research Llc Enterprise access control and accounting allocation for access networks
US11228617B2 (en) 2009-01-28 2022-01-18 Headwater Research Llc Automated device provisioning and activation
US11337059B2 (en) 2009-01-28 2022-05-17 Headwater Research Llc Device assisted services install
US20100205539A1 (en) * 2009-02-12 2010-08-12 Amivox Ehf. Instant messaging and telephony value added services
US8832777B2 (en) 2009-03-02 2014-09-09 Headwater Partners I Llc Adapting network policies based on device service processor configuration
US8606911B2 (en) 2009-03-02 2013-12-10 Headwater Partners I Llc Flow tagging for service policy implementation
US9021014B2 (en) 2009-03-25 2015-04-28 Tekelec, Inc. Methods, systems, and computer readable media for providing home subscriber server (HSS) proxy
US20100250662A1 (en) * 2009-03-25 2010-09-30 Devesh Agarwal Methods, systems, and computer readable media for providing home subscriber server (hss) proxy
US8452325B2 (en) 2009-05-11 2013-05-28 Tekelec, Inc. Methods, systems, and computer readable media for providing scalable number portability (NP) home location register (HLR)
US20100285800A1 (en) * 2009-05-11 2010-11-11 Mccann Thomas M Methods, systems, and computer readable media for providing scalable number portability (np) home location register (hlr)
US8958306B2 (en) 2009-10-16 2015-02-17 Tekelec, Inc. Methods, systems, and computer readable media for providing diameter signaling router with integrated monitoring functionality
US9647986B2 (en) 2009-10-16 2017-05-09 Tekelec, Inc. Methods, systems, and computer readable media for providing diameter signaling router with firewall functionality
US8613073B2 (en) 2009-10-16 2013-12-17 Tekelec, Inc. Methods, systems, and computer readable media for providing diameter signaling router with firewall functionality
US20110116382A1 (en) * 2009-10-16 2011-05-19 Mccann Thomas M Methods, systems, and computer readable media for providing diameter signaling router with integrated monitoring functionality
US8750292B2 (en) 2010-02-25 2014-06-10 Tekelec, Inc. Systems, methods, and computer readable media for using a signaling message routing node to provide backup subscriber information management service
US20130122821A1 (en) * 2010-07-05 2013-05-16 Telefonaktiebolaget L M Ericsson L M Ericsson (Pub Power consumption reduction in a user terminal
US8971820B2 (en) * 2010-07-05 2015-03-03 Telefonaktiebolaget L M Ericsson (Publ) Power consumption reduction in a user terminal
US8644355B2 (en) 2010-12-23 2014-02-04 Tekelec, Inc. Methods, systems, and computer readable media for modifying a diameter signaling message directed to a charging function node
US8547908B2 (en) 2011-03-03 2013-10-01 Tekelec, Inc. Methods, systems, and computer readable media for enriching a diameter signaling message
US8831016B2 (en) 2011-03-18 2014-09-09 Tekelec, Inc. Methods, systems, and computer readable media for configurable diameter address resolution
US9154826B2 (en) 2011-04-06 2015-10-06 Headwater Partners Ii Llc Distributing content and service launch objects to mobile devices
US9100796B2 (en) 2011-12-15 2015-08-04 Tekelec, Inc. Methods, systems, and computer readable media for seamless roaming between diameter and non-diameter networks
US8855654B2 (en) 2013-01-28 2014-10-07 Tekelec Global, Inc. Methods, systems, and computer readable media for tracking and communicating long term evolution (LTE) handset communication capability
US11743717B2 (en) 2013-03-14 2023-08-29 Headwater Research Llc Automated credential porting for mobile devices
US10834583B2 (en) 2013-03-14 2020-11-10 Headwater Research Llc Automated credential porting for mobile devices
US10171995B2 (en) 2013-03-14 2019-01-01 Headwater Research Llc Automated credential porting for mobile devices
US20150006723A1 (en) * 2013-06-28 2015-01-01 Alcatel-Lucent Canada Inc. Traffic detection function based on usage based thresholds
US9276863B2 (en) * 2013-06-28 2016-03-01 Alcatel Lucent Traffic detection function based on usage based thresholds
US20160072696A1 (en) * 2014-09-05 2016-03-10 Telefonaktiebolaget L M Ericsson (Publ) Forwarding table precedence in sdn
US9692684B2 (en) * 2014-09-05 2017-06-27 Telefonaktiebolaget L M Ericsson (Publ) Forwarding table precedence in SDN
US10897521B2 (en) 2017-01-19 2021-01-19 Advanced New Technologies Co., Ltd. Application-based data interaction method and apparatus
US11929907B2 (en) 2022-03-08 2024-03-12 T-Mobile Usa, Inc. Endpoint assisted selection of routing paths over multiple networks

Also Published As

Publication number Publication date
US20030035409A1 (en) 2003-02-20

Similar Documents

Publication Publication Date Title
US7039037B2 (en) Method and apparatus for providing service selection, redirection and managing of subscriber access to multiple WAP (Wireless Application Protocol) gateways simultaneously
EP1588513B1 (en) Mechanisms for policy based umts qos and ip qos management in mobile ip networks
US6785256B2 (en) Method for extending mobile IP and AAA to enable integrated support for local access and roaming access connectivity
US7277948B2 (en) Network system with dynamic service profile updating functions
US7855982B2 (en) Providing services to packet flows in a network
RU2407196C2 (en) Method and device for support of transparent proxy server service in gateway of wireless access and system equipped with such gateway
JP5080490B2 (en) Method and apparatus for route optimization in a communication network
US6819652B1 (en) Method and apparatus for processing control messages in a communications system
EP1766896B1 (en) Method and system for controlling services in a packet data network
CA2321396C (en) Mobile communications service system, mobile communications service method, authentication apparatus, and home agent apparatus
US20060114832A1 (en) Platform and method for providing data services in a communication network
JP2001224070A (en) Mobile communication system and its method
KR20070074668A (en) A default subscription profile for a roaming terminal device in a packet data based mobile communication network
JP4892062B2 (en) Method and apparatus for simultaneous registration of voice and data subscribers
CN108667879B (en) Data service session binding method, routing equipment and system

Legal Events

Date Code Title Description
AS Assignment

Owner name: TARAL NETWORKS, INC., CANADA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WANG, JIWEI R.;JAYANT, ALIN;KADAR, VINCENT;AND OTHERS;REEL/FRAME:012108/0715

Effective date: 20010802

AS Assignment

Owner name: PARTNERS FOR GROWTH, L.P., CALIFORNIA

Free format text: SECURITY AGREEMENT;ASSIGNOR:AIRWIDE SOLUTIONS INC.;REEL/FRAME:016318/0314

Effective date: 20050722

AS Assignment

Owner name: SILICON VALLEY BANK, CALIFORNIA

Free format text: SECURITY INTEREST;ASSIGNOR:AIRWIDE SOLUTIONS INC.;REEL/FRAME:016635/0209

Effective date: 20050722

STCF Information on status: patent grant

Free format text: PATENTED CASE

AS Assignment

Owner name: AIRWIDE SOLUTIONS INC., MASSACHUSETTS

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:020195/0294

Effective date: 20071127

Owner name: AIRWIDE SOLUTIONS INC., MASSACHUSETTS

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:PARTNERS FOR GROWTH, L.P.;REEL/FRAME:020195/0370

Effective date: 20071119

Owner name: AIRWIDE SOLUTIONS HOLDINGS LTD., UNITED KINGDOM

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:PARTNERS FOR GROWTH, L.P.;REEL/FRAME:020195/0370

Effective date: 20071119

Owner name: AIRWIDE SOLUTIONS UK LTD., UNITED KINGDOM

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:PARTNERS FOR GROWTH, L.P.;REEL/FRAME:020195/0370

Effective date: 20071119

Owner name: AIRWIDE SOLUTIONS NORTH AMERICA LTD., CANADA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:PARTNERS FOR GROWTH, L.P.;REEL/FRAME:020195/0370

Effective date: 20071119

Owner name: LIGHTHOUSE CAPITAL PARTNERS VI, L.P., CALIFORNIA

Free format text: SECURITY AGREEMENT;ASSIGNOR:AIRWIDE SOLUTIONS INC.;REEL/FRAME:020196/0127

Effective date: 20071129

FPAY Fee payment

Year of fee payment: 4

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

FEPP Fee payment procedure

Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: LIGHTHOUSE CAPITAL PARTNERS VI, L.P., CALIFORNIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:AIRWIDE SOLUTIONS INC.;REEL/FRAME:026355/0828

Effective date: 20110527

AS Assignment

Owner name: AIRWIDE SOLUTIONS INC., MASSACHUSETTS

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:LIGHTHOUSE CAPITAL PARTNERS VI, L.P.;REEL/FRAME:026844/0194

Effective date: 20110527

AS Assignment

Owner name: COMERICA BANK, MICHIGAN

Free format text: SECURITY AGREEMENT;ASSIGNOR:MAVENIR HOLDINGS, INC. FORMERLY KNOWN AS AIRWIDE SOLUTIONS INC.;REEL/FRAME:026999/0975

Effective date: 20110909

AS Assignment

Owner name: SILICON VALLEY BANK, TEXAS

Free format text: SECURITY AGREEMENT;ASSIGNORS:MAVENIR SYSTEMS, INC.;MAVENIR HOLDINGS, INC.;REEL/FRAME:029156/0199

Effective date: 20121018

AS Assignment

Owner name: MAVENIR HOLDINGS, INC., FORMERLY KNOWN AS AIRWIDE

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:COMERICA BANK, A TEXAS BANKING ASSOCIATION;REEL/FRAME:029178/0732

Effective date: 20121023

AS Assignment

Owner name: MAVENIR HOLDINGS, INC., TEXAS

Free format text: MERGER;ASSIGNOR:AIRWIDE SOLUTIONS INC.;REEL/FRAME:029319/0904

Effective date: 20110527

FEPP Fee payment procedure

Free format text: PAT HOLDER NO LONGER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: STOL); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

FPAY Fee payment

Year of fee payment: 8

FEPP Fee payment procedure

Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

FEPP Fee payment procedure

Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: MAVENIR INTERNATIONAL HOLDINGS, INC. FKA STOKE, IN

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:035551/0171

Effective date: 20150429

Owner name: MAVENIR SYSTEMS, INC., TEXAS

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:035551/0171

Effective date: 20150429

Owner name: MAVENIR SYSTEMS IP HOLDINGS, LLC, TEXAS

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:035551/0171

Effective date: 20150429

Owner name: MAVENIR HOLDINGS, INC., TEXAS

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:035551/0171

Effective date: 20150429

AS Assignment

Owner name: AIRWIDE SOLUTIONS INC., MASSACHUSETTS

Free format text: CHANGE OF NAME;ASSIGNOR:TARAL NETWORKS, INC.;REEL/FRAME:036332/0728

Effective date: 20040823

AS Assignment

Owner name: MITEL MOBILITY, INC., TEXAS

Free format text: MERGER AND CHANGE OF NAME;ASSIGNORS:MAVENIR HOLDINGS, INC.;MITEL MOBILITY, INC.;REEL/FRAME:036873/0095

Effective date: 20150930

FEPP Fee payment procedure

Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: CERBERUS BUSINESS FINANCE, LLC, AS COLLATERAL AGEN

Free format text: GRANT OF A SECURITY INTEREST -- PATENTS;ASSIGNOR:MAVENIR SYSTEMS, INC. (F/K/A MITEL MOBILITY INC.);REEL/FRAME:041877/0881

Effective date: 20170228

AS Assignment

Owner name: MAVENIR SYSTEMS, INC., TEXAS

Free format text: CHANGE OF NAME;ASSIGNOR:MITEL MOBILITY INC.;REEL/FRAME:042369/0185

Effective date: 20170228

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553)

Year of fee payment: 12

AS Assignment

Owner name: MAVENIR SYSTEMS, INC. (F/K/A MITEL MOBILITY INC.),

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CERBERUS BUSINESS FINANCE, LLC, AS COLLATERAL AGENT;REEL/FRAME:045773/0100

Effective date: 20180508

AS Assignment

Owner name: GOLDMAN SACHS LENDING PARTNERS LLC, AS COLLATERAL AGENT, NEW YORK

Free format text: GRANT OF SECURITY INTEREST IN PATENTS;ASSIGNOR:MAVENIR SYSTEMS, INC.;REEL/FRAME:046139/0299

Effective date: 20180508

Owner name: GOLDMAN SACHS LENDING PARTNERS LLC, AS COLLATERAL

Free format text: GRANT OF SECURITY INTEREST IN PATENTS;ASSIGNOR:MAVENIR SYSTEMS, INC.;REEL/FRAME:046139/0299

Effective date: 20180508

AS Assignment

Owner name: JPMORGAN CHASE BANK, N.A., NEW YORK

Free format text: SECURITY AGREEMENT;ASSIGNOR:MAVENIR SYSTEMS, INC.;REEL/FRAME:057221/0801

Effective date: 20210818

Owner name: MAVENIR SYSTEMS, INC., TEXAS

Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL - RELEASE OF 046139.0299;ASSIGNOR:GOLDMAN SACHS LENDING PARTNERS LLC, AS COLLATERAL AGENT;REEL/FRAME:057222/0398

Effective date: 20210818