US20060041931A1 - Service level assurance system and method for wired and wireless broadband networks - Google Patents

Service level assurance system and method for wired and wireless broadband networks Download PDF

Info

Publication number
US20060041931A1
US20060041931A1 US11/089,238 US8923805A US2006041931A1 US 20060041931 A1 US20060041931 A1 US 20060041931A1 US 8923805 A US8923805 A US 8923805A US 2006041931 A1 US2006041931 A1 US 2006041931A1
Authority
US
United States
Prior art keywords
client
network
user device
server
spi
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US11/089,238
Other languages
English (en)
Inventor
Robert Boxall
Vojislav Samsalovic
Biju Nair
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.)
Smith Micro Software Inc
Original Assignee
PCTel Inc
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 PCTel Inc filed Critical PCTel Inc
Priority to US11/089,238 priority Critical patent/US20060041931A1/en
Assigned to PCTEL, INC. reassignment PCTEL, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BOXALL, ROBERT, NAIR, BIJU, SAMSALOVIC, VOJISLAV
Publication of US20060041931A1 publication Critical patent/US20060041931A1/en
Assigned to PCTEL, INC. reassignment PCTEL, INC. CORRECTIVE COVERSHEET TO CORRECT ASSIGNMENT PREVIOUSLY RECORDED ON REEL 016950, FRAME 0623. Assignors: BOXALL, ROBERT, NAIR, BIJU, SAMSALOVIC, VOJISLAV
Assigned to SMITH MICRO SOFTWARE, INC. reassignment SMITH MICRO SOFTWARE, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: PCTEL, INC.
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/403—Bus networks with centralised control, e.g. polling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5061—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the interaction between service providers and their network customers, e.g. customer relationship management
    • H04L41/5067—Customer-centric QoS measurements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5061—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the interaction between service providers and their network customers, e.g. customer relationship management
    • H04L41/507—Filtering out customers affected by service problems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/091—Measuring contribution of individual network components to actual service level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/12—Network monitoring probes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/16—Implementing security features at a particular protocol layer
    • H04L63/162—Implementing security features at a particular protocol layer at the data link layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/52—Network services specially adapted for the location of the user terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H04W12/062—Pre-authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/14—Flow control between communication endpoints using intermediate storage
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/18—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup

Definitions

  • the present invention relates generally to systems and methods for network management, and more particularly relates to systems and methods for monitoring and managing the quality of service of a broadband service offering.
  • SLA Service Level Assurance
  • broadband providers typically continuous monitor and attempt to improve the quality of their service offerings.
  • Various methods are used for determining quality of service, all of which typically involve monitoring various network parameters. Among the network parameters that are typically monitored are: number of connect attempts, connection location (hot spot, dial up node, Ethernet node), signal strength, data rates (effective as well as available), connection duration, and so on.
  • a system and method are provided for tracking and reporting the performance of a network.
  • a client or a user device can access the network through a wired connection or wireless access points.
  • the client maintains a log or track the events that occur during the log-on attempts as well as the communication sessions as well as other data related to the network performance.
  • During the communication session data can be transferred between the client and a network device, such as the central server or a database, in the network, regardless of whether the network device is trusted and secure or not secure.
  • FIG. 1 illustrates in block diagram form the interoperation of the present invention with a service provider's network operations center;.
  • FIG. 2 illustrates in block diagram form an exemplary CCS architecture in accordance with the present invention
  • FIG. 3 illustrates in time line form an exemplary SPI client-server transaction where the SPI server is in the network provider's “Whitespace”;
  • FIG. 4 illustrates in block diagram form an exemplary SPI client-server transaction where the SPI server is not in the network provider's “Whitespace”;
  • FIG. 5 illustrates a simple message exchange sequence between the SPI client and the SPI server
  • FIG. 6 illustrates a message exchange between the SPI client and the SPI server involving authentication
  • FIG. 7A-7D illustrate an authentication sequence in an exemplary implementation of the present invention.
  • FIG. 8 is a flow chart for the process of authenticating a client.
  • the network management system (NMS) 100 of the present invention interacts with one or more devices 110 A-n (sometimes collectively referred to hereinafter as “devices 110 ”), which have been suitably configured to provide quality of service information to the NMS 100 .
  • the NMS 100 in turn communicates with the network operation center (NOC) 120 , which is not part of the invention and is typically resident at the premises of a network service provider.
  • NOC network operation center
  • Devices 110 A-n include computers having thereon a “roaming client” functionality, which includes Service Provider Interface (SPI) functionality, or a PDA, a Cell phone, a camera, an MP3 device, or any other network connected device or appliance capable with SPI functionality, that is, capable of contacting the NMS 100 and then executing appropriate commands received back from the NMS 100 including responding to queries with appropriate status information.
  • a “roaming client” functionality which includes Service Provider Interface (SPI) functionality, or a PDA, a Cell phone, a camera, an MP3 device, or any other network connected device or appliance capable with SPI functionality, that is, capable of contacting the NMS 100 and then executing appropriate commands received back from the NMS 100 including responding to queries with appropriate status information.
  • SPI Service Provider Interface
  • the NMS 100 includes, in an exemplary arrangement, three functional components, designated in FIG. 1 as a Central Configuration Server (CCS) 130 , a SPI 140 , and a Service Level Assurance (SLA) module 150 .
  • CCS Central Configuration Server
  • SPI Service Level Assurance
  • the exchange between an SPI-enabled device 110 and the SLA module 150 begins when an SPI-enabled device 110 provides information such as, for example, ID, location, IP address, and/or other relevant information.
  • the SLA module 150 queries, via the SPI 140 and CCS 150 , the appropriate SPI enabled devices 110 A-n, which in turn responds to the queries and provide appropriate information concerning location, connect attempts, failures, signal strength, available and effective data rates, and any other status or location information which the carrier deems appropriate.
  • the SPI 140 gathers the responses from the SPI-enables devices 110 A-n and, if necessary, formats the information for forwarding to the NOC.
  • the NOC includes appropriate functionality to accumulate the data from the SPI-enabled devices 110 A-n, and generate appropriate reports for management of the network resources. It will be appreciated that the foregoing approach has the advantage of allowing communication between the SLA module 150 and compatible, SPI-enabled devices 110 even if the SPI-enabled devices 110 are behind a firewall, because the protocol is text-based and is carried over standard HTTP(S) ports, typically ports 80 and 443 .
  • the present invention enables the client or device 110 to communicate with the NOC.
  • the functionality provided by the present invention also allows the NOC to communicate, through the NMS 100 , back to the SPI enabled devices 110 .
  • the NOC may desire to instruct the client or device 110 to perform various functions, for example launching a browser or other application, or directing users to a particular web page.
  • the operation may also include a push of content to the end user, or an upload or download of files, for example software upgrades, from a desired location, which may be either pre-arranged or specified on the fly.
  • One particular instance of redirecting a client device 110 may be to enable further communications. For example, if an account is not active, the NOC may direct the SPI-enabled device 110 to a provisional URL or other web page so that that user can obtain an account or otherwise establish credentials.
  • One aspect of the invention is the client-side functionality, represented generally at 110 A-n by the roaming client module or software indicated at 110 A-B, which includes SPI enablement, and by which network connectivity is achieved for a variety of SPI-enabled devices 110 A-n as described above.
  • the SPI capabilities incorporated into the roaming client and other SPI-enabled devices 110 include: aggregation of disparate wireless networks under one service umbrella; prioritization of wireless networks; support for seamless roaming between networks, including Wi-Fi and GPRS; support for automatic authentication between networks that have complex and non standard mechanisms for user authentication and administration; access Point Location database; and, automatic and remote update of network attributes, location database, and Roaming Client software updates. It will be appreciated by those skilled in the art that the SPI could easily be expanded to include other capabilities.
  • the SPI-enabled roaming client module 110 further includes several features that are remotely updateable and/or upgradeable, including the executable software, location finder database, roaming partner data, carrier/PCOEM/enterprise preferences, user interface skins, and hardware drivers.
  • the CCS 130 allows carriers, PC-OEMs, and Enterprises to manage the storage and flow of updates and upgrades to clients from a single location, and can further provide reporting and tools to manage the ability to push new data to clients.
  • the CCS 130 operates to provide version control, code management, and flow control for all updateable features within the Roaming Client software.
  • the CCS 130 allows management and manipulation of “Hotspot” location database information, roaming partner database information, and the gated upload capabilities for these databases.
  • the CCS 130 also allows the carrier, PCOEM, or Enterprise to manage versioned software files, such as executable files of the Roaming Client application and user interface skins.
  • the CCS 130 can be used in conjunction with the Roaming Client to update other files on a user's PC that are not directly related to the roaming client application, such as device drivers.
  • the CCS 130 also negotiates download parameters, such as bandwidth, frequency, and duration of downloads with each client, based on rules that are predetermined by the carrier, PCOEM, Enterprise, or configured by the end user.
  • the CCS 130 may be thought of as a secure, web-based administrative console, which provides the capability for updating the various pre-defined and provider-specific parameters for the Roaming Client.
  • the CCS 130 allows management and manipulation of “Hotspot” location database information, roaming partner database information, and the gated upload capabilities for these databases. Together, the combination of the CCS 130 with the user connectivity tool of the Roaming Client provides a dynamic wireless access management solution.
  • the CCS 130 may be architected based on the J2EE framework. In at least such an implementation, the CCS 130 need not use a middle tier or business tier, and therefore need not include an Enterprise Java Beans server.
  • the CCS 130 functionality may reside on a personal computer or a Sun SPARC workstation, or similar computing platform, and any suitable operating system such as Windows, Linux or Solaris.
  • Typical software requirements for such an exemplary arrangement include compatibility with a Java Servelet specification, for example version 2.3, and a JSP application such as version 1.2, as well as with a suitable database server, for example Microsoft SQL Server 2000 or similar. It may also be desirable to include compatibility with JDK 1.4.1 or later, at least for application servers.
  • the CCS architecture 200 includes an operating system layer 210 that communicates with the selected operating system (not shown), which in the illustrated example is Windows 2000 Advanced Server.
  • a web application server 220 which may for example be based on the J2EE standard and certified on Jakarta Tomcat, layers atop the OS layer 210 , as does a database module 230 , which may, for example, be compliant with SQL 2000 and certified on MS SQL Server. Layered atop the application server module 220 and database module 230 are various modules for managing connections via different protocols. Thus, for example, Wi-Fi connection data is managed at 240 , GPRS connection data is managed at 250 , Location Finder data is managed at 260 , and Custom Application data is managed at 270 .
  • the SPI 140 operates to provide the device 110 access to a network, such as through an access point (AP) located at a hotspot.
  • AP access point
  • WiFi hotspots a Service Provider typically has hundreds if not thousands of different locations that a user can connect to. These locations may be maintained by the service provider or provided by a roaming agreement with another provider.
  • a user arrives at a location, connects to the network, and then launches their WEB browser.
  • the user attempts to get to the Internet, but is then captured and redirected by the local network administration server (NAS) device, whereupon the user is requested to authenticate or sign up and pay for service.
  • NAS network administration server
  • the SPI protocol allows additional steps to be performed.
  • the basic goal of the SPI protocol is to allow the Roaming Client the ability to communicate to the service provider before and after login into a local hotspot. This client/server communication allows a service provider to perform various checks on the client, and push back different actions for the client to execute depending on the Roaming Clients state.
  • the SPI 140 provides a client/server communications protocol, and can be implemented on any web server that supports such a protocol.
  • the SPI protocol allows a trusted web server to execute actions on the devices 110 .
  • the SPI protocol may, for example, be an XML-based messaging protocol that uses HTTPS as the primary transport for secure communications between the client and server.
  • the SPI 140 and CCS 130 interact in that the CCS 130 is the mechanism that allows a provider to modify specific parameters on the client, while the SPI protocol is the mechanism that allows specific actions to be executed on the client, for example, login and authentication in some embodiments. Such actions may use parameters that are pushed to the client via the CCS interface.
  • a provider deploys a hotspot and deploys a server that supports the SPI protocol.
  • a user associates with the hotspot and physically establishes a connection between the client machine and the hotspot.
  • Wi-Fi there is a notion of physical “connection” to a hotspot although the user has not authenticated.
  • the Roaming Client is considered to be in the “Connected” state (although not yet authenticated).
  • the Roaming Client can initiate communication to the provider's SPI server to inform the server about its current state and other attributes associated with the client.
  • the Roaming Client will only initiate SPI transactions to servers that are considered “trusted”, or in the providers “White List”. This will allow the provider to send back to the Client pre-authentication actions to be executed. After authentication, the client will again post its INFO status to the SPI server, allowing post-authentication actions to be executed by the client. Finally, when the client disconnects, final messages can be executed related to disconnection from the network.
  • Examples of pre-authentication actions that a client may execute using SPI 140 include, but are not limited to, provisioning a new user, pushing surcharge information to a client, requesting statistics from the client, and prompting a user for a password.
  • Post-authentication actions includes pushing the time remaining, pushing advertising, pushing a custom skin, and pushing a message.
  • Examples of disconnect actions includes sending log-off data, such as a thank you or other message, and sending usage statistics. It will be appreciated that such actions can be provided to the NOC in accordance with the present invention to provide dynamic monitoring and data gathering.
  • the SPI protocol is shown in an exemplary arrangement, wherein the SPI protocol is primarily based on two message packages: INFO and ACTION.
  • the INFO or information message communicates from the client to the SPI server the client's current status.
  • The, ACTION message communicates from the server to the client an action that the SPI server wants the client to execute.
  • an INFO message may comprise, for example, ⁇ status> the current state of the client ⁇ /status> ⁇ username>username ⁇ /username> ⁇ password>password of user ⁇ /password> ⁇ error> reported error code ⁇ /error> ⁇ provider> the name of the service provider ⁇ /provider> ⁇ location>Geographic location of basestation ⁇ /location> ⁇ sessionid> session id generated ⁇ /sessionid> ⁇ ip> ip address of users device ⁇ /ip> ⁇ mac> MAC address of users adapter ⁇ /mac> ⁇ bssid>access point mac address ⁇ /bssid> ⁇ linkspeed>reported link speed from basestation ⁇ /linkspeed> ⁇ rssi>reported signal strength from basestation ⁇ /rssi> ⁇ hwvendor>hardware vendor of basestation ⁇ /hwvendor> ⁇ driverversion>software driver version ⁇ /driverversion> ⁇ hostname>basestation host name ⁇ /host
  • the Roaming Client initiates communication with the SPI Protocol Server.
  • the SPI server will be a web server deployed to communicate with and manage SPI enabled devices, such as the Roaming Client or other devices 110 .
  • the SPI Server is a functionality, which may reside on a dedicated hardware server, or may coexist with other software functions on one or more hardware servers, each of which may be a PC, a workstation, or similar computer processing device.
  • the SPI message 600 describes an idealized login scenario for a user who has an already-existing subscription and has successfully logged in at a particular carrier's hotspot and completed the upload successfully.
  • the transactions described in this section happen in an automated fashion when the client or MMD arrives at a hotspot hosted by a wireless service provider, the following sequence happens with no or limited user interaction.
  • Client Request 602 the user attempts to go to a particular website, for example www.mystorage.mywireless.com/myaccount, using an SPI component embedded in the MMD.
  • NAS Response 604 the NAS responds with a redirect because the MMD is not authenticated.
  • Client Request 606 which is the INFO portion of the SPI enable client device communication with the NMS ( FIG. 5 )
  • SPI Server Response 608 the SPI server responds with an Action message as required by the protocol definition.
  • the SPI server sends an Action message to the client, in this case “login” action, which also contains a URL to the authentication server in the form of a parameter name/value pair in the login message.
  • the client parses the action message and then responds with a POST request to the authentication server URL providing the user name and password or a single unique device code embedded in the device.
  • the authentication server responds with a successful login message.
  • the client sends a start upload request.
  • the server responds with a start upload command sending the upload location URL as a parameter.
  • the client MMD parses the location URL and begins upload to that location.
  • the server responds with an affirmative on upload complete.
  • FIGS. 7A-7D A further example of authentication is shown in FIGS. 7A-7D , with an attempt to connect to an Acme Company server.
  • the user connects to Acme's wireless network through Acme's AP.
  • the user makes a request to a URL outside of Acme's “white list” of “free” servers.
  • the request passes through to the Acme's Network Access Server (NAS), which verifies whether the user has been authenticated.
  • NAS Network Access Server
  • CCS attributes initially pushed to the SPI-enabled device are used by the SPI device as the parameters for connecting to the network.
  • the Roaming Client 110 will use parameters pushed to it from CCS during client updates for authentication purposes.
  • HTTP headers provided by the network may be used to provide the SPI device with operating parameters.
  • the Roaming Client can also parse attributes from the network in real time.
  • a provider may use an authentication API that specifies attribute values utilizing http headers.
  • Acme's NAS responds back to the client's original request with an UNAUTHORIZED response with custom HTTP headers.
  • the custom HTTP headers could have also been returned after the client connected to the URL in the redirect request. Regardless of how the headers are provided, these headers will then be utilized in the next step of the authentication process, shown in FIG. 7B .
  • the client parses the information from the NAS response, then initiates an http request to the SPI server to report the client's status as part of the INFO package message.
  • the SPI server URL was previously provided by the CCS in a Client update Configuration.
  • the INFO package below represents the message that the client will send to the SPI server in this example.
  • the SPI server then responds with an Action message appropriate for the client's current state, as well as other variables in the INFO message package, as shown in FIG. 7C .
  • the SPI server responds with an Action message to prompt the user for credentials, execute a login, then send an INFO message package back to the SPI server.
  • each action will be executed in the order received.
  • the client then executes the actions specified by the SPI server.
  • the client prompts the user for username and password (credentials), and then executes the “login” action directive.
  • username and password a specific action is sent by the Acme's SPI server to direct the client to prompt the user to input the username and password: ⁇ action>promptCredentials ⁇ /action>.
  • the client When the client receives the ⁇ action>logon ⁇ /action> directive, it posts the credential information to the URL provided by the NAS (see above) or use the value pushed down to the client by the CCS. In either case, the authentication method that is implemented must be able to utilize this value when the login method is executed.
  • the provider has implemented a custom authentication method on the client using the Authentication API. The authentication method utilizes the custom parameter AcmeWirelessLogin-URL, which was provided by the NAS device previously, see FIG. 7B .
  • the login action is executed, and the credentials are sent to the authentication server URL.
  • the Authentication server then completes the transaction with an authentication response to the client.
  • the process of authentication of a client begins at step 800 .
  • the client initiates a communication session with an access point device or an access point interface (API) and attempts to access the Internet.
  • the API determines, based on communication with the service provider's authentication server and the associated database, if the client is an authenticated client. If so, then at step 806 the client is allowed to access the desired URL. If not, then at step 808 the client is directed to an SPI resident on a NMS. It will be apparent to one of skill in the art that the SPI may be operating on its own server and not as part of the NMS and hence be a stand alone server.
  • the SPI of the NMS queries the client for information and the client provides the relevant information for authentication.
  • the SPI of the NMS pushes an ACTION to the client for automatic sign-on and the URL necessary for the communication session.
  • the process continues at step 806 until the client initiates termination of the communication session.
  • the SPI of the NMS receives the termination request and determines if the termination and logoff process should be initiated. If not, then the process remains at step 814 until it is time to initiate the termination process.
  • the SPI of the NMS pushes a termination ACTION to the client. The client terminates the session and disconnects from the AP.
  • the INFO message can be configured to provide to the NMS 100 ( FIG. 1 ) a variety of information suitable for monitoring and management of a network.
  • the client can be configured to maintain an event log containing a record of various events, which can be uploaded to the NOC 120 through the NMS 100 upon request.
  • Table 1 shows, for an exemplary arrangement only, a combined list of the types of information which can be either delivered as part of the INFO message, or maintained in an event log and uploaded upon request:
  • Parameter Name Description XML Syntax Example status
  • the Status attribute ⁇ status>loggedin ⁇ /status> provides information about the client to the server side logic and to allow the server to determine a set of actions that should be performed by the client.
  • the possible states that are supported in the status element are listed in “Table 2: Supported Status Attributes” below.
  • username Username information ⁇ username>someuser ⁇ /username> allows access to the user's account and displaying of appropriate content for user account status. If not provided, the server assumes this is a new customer.
  • a link may be provided allowing existing users to enter existing username/password manually.
  • realm The realm attribute as ⁇ realm>@provider.com ⁇ /realm> entered by the user or inserted by the client that represents the realm the user is authenticating to.
  • password Password information is ⁇ password>somepass ⁇ /password> required for accessing user's account. If not provided, the server should prepopulate username field and prompt user to enter password before being able to access account info.
  • error Error codes provide ⁇ error>0 ⁇ /error> additional information Error Codes Vary with about the client status access mode. and why that condition occurred. Error codes are relative to the technology that is currently being used: Wi-Fi error codes are generated by the local AP based on API method i.e.
  • WISPr GPRS error codes are generated either by the dial in RAS server or the GPRS network. Modem error codes are generated by the dial in RAS.
  • provider Provider identifier passed ⁇ provider>CarrierXYZ ⁇ /provider> by the local NAS.
  • location Location identifier passed ⁇ location>wp_700 ⁇ /location> by the local NAS.
  • sessionid Session identifier passed ⁇ sessionid>12345 ⁇ /sessionid> by the local NAS. In some instances the session id may be generated by RADIUS. Session id will be collected if present, although many providers may not generate a session id.
  • securitytype The type of security used ⁇ securitytype>EAP- in the authentication of TTLS ⁇ /securitytype> the user to the network. Possible values: Empty Field WEP-Open WEP-Closed EAP-TTLS EAP-TLS EAP-PEAP EAP-LEAP EAP-TKIP EAP-PSK ip Current IP address of the ⁇ ip>192.168.11.1 ⁇ /ip> client machine. mac MAC address assigned to ⁇ mac>AA-BB-CC-DD-EE-FF ⁇ /mac> the client machine.
  • bssid The base station (Access ⁇ bssid>AA-BB-CC-DD-EE-FF ⁇ /bssid> Point) id linkspeed The reported link speed in ⁇ linkspeed>11000000 ⁇ /linkspeed> bps. i.e. 11 Mbps Wi-Fi connections is reported as 11000000. 56 Kbps modem connection is reported as 56000. rssi The reported signal ⁇ rssi> ⁇ 48 ⁇ /rssi> strength as reported by the adapter in dBm. hwvendor The adapter vendor as ⁇ hwvendor>acme_ap ⁇ /hwvendor> reported by the adapter.
  • driverversion The driver version as ⁇ driverversion>1.2.43.2 ⁇ /driverversion> reported by the adapter.
  • hostname The reported hostname of ⁇ hostname>acme_wireless the AP ⁇ /hostname> popid POP user identifier ⁇ popid> ⁇ /popid> information. This field Dial Connection only contains the unique user id the provider assigns to each user.
  • bdial Blind dial is set to ‘N’ for ⁇ bdial>Y ⁇ /bdial> No Blind dial or ‘Y’ to indicate a Blind dial. This information is supported in Analog, ISDN, DoPA and PIAFS access modes. BDIAL will be set to ‘N’ by default.
  • clientversion Version of the client. ⁇ clientversion>1.3.2.1234 ⁇ /clientversion> Format: w.x.y.z w Major Software version loccode It indicates the Country ⁇ loccode>44+207 ⁇ /loccode> code and Area code.
  • clientid Unique client identifier ⁇ clientid>1234567890 ⁇ /clientid> provided by the client.
  • devtype The device type used for ⁇ devtype>wifi ⁇ /devtype> accessing the network. Possible modes are: wifi, gprs, isdn, dsl, cable, phs, ethernet, modem. phonenumber Full Phone number string ⁇ phonenumber>011+44+ used for the connection. 207+12345678 ⁇ /phonenumber> The Phone number used for the connection in case of Analog, ISDN, PHS access modes shall be provided.
  • overphone An alternate override ⁇ phonenumber>011+44+ phone number that is 207+12345678 ⁇ /phonenumber> used as in for Analog, ISDN, PHS access modes. os Operating system on ⁇ os> ⁇ /os> which the client is installed.
  • one exemplary implementation implements only the following data in the INFO message, and leaves the remaining data for an event log: status, username, password, realm, error, provider, location, session, IP, MAC, bssid, linkspeed, rssi, hwvendor, driverversion, hostname, eventhistory, clientid, and clientversion.
  • loggedin Client has successfully ⁇ status>loggedin ⁇ /status> performed Login operations using Login API.
  • loginfailed Client has attempted ⁇ status>loginfailed ⁇ /status> Login operations, but the login has failed due to an error or some other known or unknown problems.
  • loggedout Client has successfully ⁇ status>loggedout ⁇ /status> performed Logout operations using Login API.
  • logoutfailed Client has attempted ⁇ status>logoutfailed ⁇ /status> Logout operations, but the logout has failed due to an error or some other known or unknown problems.
  • disconnecting Client has logged off and ⁇ status>disconnecting is about to physically ⁇ /status> disconnect from the network. This status will only be applicable in instances where the client still has network visibility although not authenticated.
  • Various custom parameters can be used for management or authentication actions on the Roaming Client.
  • either of two methods can be used to update or manage attributes on the client.
  • a CCS can push attribute values to the client when the client contacts the server for updates. It will be appreciated that, in the alternative, the CCS may simply cause a second server to push the values, or the CCS may be comprised of multiple servers.
  • WISPr authentication may be used.
  • the network provider can send custom HTTP headers to SPI-enabled devices, and the devices can parse the headers to identify the appropriate parameters. Examples of such includes login URL, location ID information, provider name, and so on.
  • An example of a custom HTTP header is shown below: HTTP/1.0 404 UNAUTHORIZED Server: MC SSG/0.0.0 (Linux) Location: http://www.acme.come/index.htm MacAddr:AA-BB-CC-DD-EE-FF&IpAddr:192.168.11.1 ...
  • the present invention provides a powerful, flexible, scalable method and system for monitoring and maintaining wired and wireless networks, including providing metrics for meeting SLA requirements, QoS requirements, or other network parameters.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Environmental & Geological Engineering (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Mobile Radio Communication Systems (AREA)
US11/089,238 2004-03-23 2005-03-23 Service level assurance system and method for wired and wireless broadband networks Abandoned US20060041931A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/089,238 US20060041931A1 (en) 2004-03-23 2005-03-23 Service level assurance system and method for wired and wireless broadband networks

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US55598804P 2004-03-23 2004-03-23
US55581204P 2004-03-23 2004-03-23
US11/089,238 US20060041931A1 (en) 2004-03-23 2005-03-23 Service level assurance system and method for wired and wireless broadband networks

Publications (1)

Publication Number Publication Date
US20060041931A1 true US20060041931A1 (en) 2006-02-23

Family

ID=35064377

Family Applications (2)

Application Number Title Priority Date Filing Date
US11/089,238 Abandoned US20060041931A1 (en) 2004-03-23 2005-03-23 Service level assurance system and method for wired and wireless broadband networks
US11/088,500 Active 2029-07-28 US8325625B2 (en) 2004-03-23 2005-03-23 Method and system for automatic data transfer on a network-connected device

Family Applications After (1)

Application Number Title Priority Date Filing Date
US11/088,500 Active 2029-07-28 US8325625B2 (en) 2004-03-23 2005-03-23 Method and system for automatic data transfer on a network-connected device

Country Status (4)

Country Link
US (2) US20060041931A1 (de)
EP (2) EP1761866A4 (de)
KR (2) KR20060135910A (de)
WO (2) WO2005094463A2 (de)

Cited By (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060002350A1 (en) * 2004-07-02 2006-01-05 Cyrus Behroozi Access point control of client roaming
US20060018328A1 (en) * 2004-07-23 2006-01-26 Comcast Cable Holdings, Llc Method and system for powerline networking
US20070055725A1 (en) * 2005-09-07 2007-03-08 Gianluca Bernardini Method, system and computer program for providing web pages based on client state
US20070213033A1 (en) * 2006-03-10 2007-09-13 Samsung Electronics Co., Ltd. Method and apparatus for authenticating mobile terminal on handover
US20070242657A1 (en) * 2006-04-12 2007-10-18 Waisman-Diamond Martin V System and method for linking existing WI-FI access points into a single unified network
US20080130601A1 (en) * 2006-12-01 2008-06-05 Electronics And Telecommunications Research Institute Method for providing network communication service with constant quality regardless of being in wired or wireless network environment
US20090064306A1 (en) * 2007-08-27 2009-03-05 Microsoft Corporation Network access control based on program state
US20100094997A1 (en) * 2005-06-23 2010-04-15 Joey Chou Event logging techniques for broadband wireless access networks
US20100263022A1 (en) * 2008-10-13 2010-10-14 Devicescape Software, Inc. Systems and Methods for Enhanced Smartclient Support
US20110087958A1 (en) * 2009-10-14 2011-04-14 Dumitru Dan Mihai Method for extracting document data from multiple sources for display on a communication device
US20130007868A1 (en) * 2011-06-30 2013-01-03 Cable Television Laboratories, Inc. Zero sign-on authentication
US8495714B2 (en) 2011-07-20 2013-07-23 Bridgewater Systems Corp. Systems and methods for authenticating users accessing unsecured wifi access points
WO2014051774A1 (en) * 2012-09-26 2014-04-03 Intel Corporation Techniques for fractional wireless broadband usage
US8910300B2 (en) 2010-12-30 2014-12-09 Fon Wireless Limited Secure tunneling platform system and method
US20160080486A1 (en) * 2014-09-17 2016-03-17 Ca, Inc. Crowdsourcing-based detection, identification, and tracking of electronic devices
US9326138B2 (en) 2006-09-06 2016-04-26 Devicescape Software, Inc. Systems and methods for determining location over a network
US9432920B2 (en) 2006-09-06 2016-08-30 Devicescape Software, Inc. Systems and methods for network curation
US9680872B1 (en) 2014-03-25 2017-06-13 Amazon Technologies, Inc. Trusted-code generated requests
US9826102B2 (en) 2006-04-12 2017-11-21 Fon Wireless Limited Linking existing Wi-Fi access points into unified network for VoIP
US9854001B1 (en) * 2014-03-25 2017-12-26 Amazon Technologies, Inc. Transparent policies
US20220361109A1 (en) * 2021-05-10 2022-11-10 Microsoft Technology Licensing, Llc System and method for reducing power consumption

Families Citing this family (56)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101161164B1 (ko) 2004-02-20 2012-07-02 뉘앙스 커뮤니케이션즈, 인코포레이티드 이동장치상의 고객 셀프 지원용과 같은 콜 인터셉트 방법
US7314169B1 (en) * 2004-09-29 2008-01-01 Rockwell Automation Technologies, Inc. Device that issues authority for automation systems by issuing an encrypted time pass
US7716489B1 (en) * 2004-09-29 2010-05-11 Rockwell Automation Technologies, Inc. Access control method for disconnected automation systems
US9275052B2 (en) 2005-01-19 2016-03-01 Amazon Technologies, Inc. Providing annotations of a digital work
WO2007070837A2 (en) 2005-12-13 2007-06-21 Snapin Software Inc. Method for performing interactive services on a mobile device, such as time or location initiated interactive services
US7289830B2 (en) * 2005-03-18 2007-10-30 Lear Corporation System and method for vehicle module wake up in response to communication activity
TW200634627A (en) * 2005-03-31 2006-10-01 Acer Inc Method of automatically opening particular types of files
EP1908041A4 (de) 2005-06-24 2014-08-27 Nuance Communications Inc Lokal-abfangverfahren wie zum beispiel anwendungen zum bereitstellen von kundenhilfe für training, informationsbesuche und diagnose
US8682298B2 (en) * 2005-10-12 2014-03-25 Nuance Communications, Inc. Message intercept methods, such as for customer self-support on a mobile device
US8352449B1 (en) 2006-03-29 2013-01-08 Amazon Technologies, Inc. Reader device content indexing
US20080046435A1 (en) * 2006-08-18 2008-02-21 Microsoft Corporation Service discovery and automatic configuration
US8554830B2 (en) * 2006-09-06 2013-10-08 Devicescape Software, Inc. Systems and methods for wireless network selection
US8743778B2 (en) * 2006-09-06 2014-06-03 Devicescape Software, Inc. Systems and methods for obtaining network credentials
US8549588B2 (en) * 2006-09-06 2013-10-01 Devicescape Software, Inc. Systems and methods for obtaining network access
US9672533B1 (en) 2006-09-29 2017-06-06 Amazon Technologies, Inc. Acquisition of an item based on a catalog presentation of items
US8725565B1 (en) 2006-09-29 2014-05-13 Amazon Technologies, Inc. Expedited acquisition of a digital item following a sample presentation of the item
US7865817B2 (en) 2006-12-29 2011-01-04 Amazon Technologies, Inc. Invariant referencing in digital works
WO2008086320A1 (en) 2007-01-05 2008-07-17 Snapin Software Inc. Methods of interacting between mobile devices and voice response systems
KR100934989B1 (ko) 2007-01-31 2009-12-31 삼성전자주식회사 컨텐츠 관리 방법 및 장치
US20080243788A1 (en) * 2007-03-29 2008-10-02 Reztlaff James R Search of Multiple Content Sources on a User Device
US9665529B1 (en) 2007-03-29 2017-05-30 Amazon Technologies, Inc. Relative progress and event indicators
US7716224B2 (en) 2007-03-29 2010-05-11 Amazon Technologies, Inc. Search and indexing on a user device
WO2008128119A1 (en) 2007-04-12 2008-10-23 Snapin Software Inc. System and method for detecting mutually supported capabilities between mobile devices
US7921309B1 (en) 2007-05-21 2011-04-05 Amazon Technologies Systems and methods for determining and managing the power remaining in a handheld electronic device
US8589149B2 (en) 2008-08-05 2013-11-19 Nuance Communications, Inc. Probability-based approach to recognition of user-entered data
JP5632380B2 (ja) * 2008-10-13 2014-11-26 デバイススケープ・ソフトウェア・インコーポレーテッド ネットワークを識別するためのシステム及び方法
US9087032B1 (en) 2009-01-26 2015-07-21 Amazon Technologies, Inc. Aggregation of highlights
US8378979B2 (en) * 2009-01-27 2013-02-19 Amazon Technologies, Inc. Electronic device with haptic feedback
US8832584B1 (en) 2009-03-31 2014-09-09 Amazon Technologies, Inc. Questions on highlighted passages
US8452858B2 (en) * 2009-05-15 2013-05-28 Novatel Wireless, Inc. Method and apparatus for loading landing page
US8692763B1 (en) 2009-09-28 2014-04-08 John T. Kim Last screen rendering for electronic book reader
US8484661B2 (en) * 2010-03-19 2013-07-09 At&T Mobility Ii Llc Agnostic execution cluster for an agnostic execution environment
US9107140B2 (en) 2010-08-13 2015-08-11 At&T Mobility Ii Llc Carrier-driven bearer path selection
US9495322B1 (en) 2010-09-21 2016-11-15 Amazon Technologies, Inc. Cover display
EP2466852A1 (de) * 2010-12-17 2012-06-20 Swisscom AG Digitale Inhaltsverwaltung
JP5185361B2 (ja) * 2010-12-28 2013-04-17 株式会社東芝 通信装置、ホスト装置、通信制御方法及び通信制御プログラム
US9158741B1 (en) 2011-10-28 2015-10-13 Amazon Technologies, Inc. Indicators for navigating digital works
US9253176B2 (en) 2012-04-27 2016-02-02 Intralinks, Inc. Computerized method and system for managing secure content sharing in a networked secure collaborative exchange environment
US9251360B2 (en) 2012-04-27 2016-02-02 Intralinks, Inc. Computerized method and system for managing secure mobile device content viewing in a networked secure collaborative exchange environment
US9553860B2 (en) 2012-04-27 2017-01-24 Intralinks, Inc. Email effectivity facility in a networked secure collaborative exchange environment
AU2013251304B2 (en) 2012-04-27 2018-12-20 Intralinks, Inc. Computerized method and system for managing networked secure collaborative exchange
KR101446319B1 (ko) * 2012-11-06 2014-10-01 주식회사 씨제이헬로비전 어플리케이션 업데이트 서비스 방법 및 시스템
US9317522B2 (en) 2013-01-07 2016-04-19 Google Inc. Saving files from third-party systems directly to a cloud storage system
US8631325B1 (en) 2013-08-09 2014-01-14 Zoomdata, Inc. Real-time data visualization of streaming data
US20150095776A1 (en) * 2013-10-01 2015-04-02 Western Digital Technologies, Inc. Virtual manifestation of a nas or other devices and user interaction therewith
US9514327B2 (en) 2013-11-14 2016-12-06 Intralinks, Inc. Litigation support in cloud-hosted file sharing and collaboration
GB2521381A (en) * 2013-12-18 2015-06-24 Mastercard International Inc Automatic data transfer
US9648100B2 (en) * 2014-03-05 2017-05-09 Commvault Systems, Inc. Cross-system storage management for transferring data across autonomous information management systems
WO2015164521A1 (en) 2014-04-23 2015-10-29 Intralinks, Inc. Systems and methods of secure data exchange
US9251276B1 (en) 2015-02-27 2016-02-02 Zoomdata, Inc. Prioritization of retrieval and/or processing of data
CN105045570A (zh) * 2015-05-22 2015-11-11 国云科技股份有限公司 一种Linux环境下多jdk版本配置多tomcat应用的方法
US10033702B2 (en) 2015-08-05 2018-07-24 Intralinks, Inc. Systems and methods of secure data exchange
US20180114239A1 (en) * 2016-10-21 2018-04-26 Mastercard International Incorporated Methods, systems, and computer readable media for electronically determining broadband network service rates in a designated area
US9942312B1 (en) 2016-12-16 2018-04-10 Zoomdata, Inc. System and method for facilitating load reduction at a landing zone
US10249295B2 (en) 2017-01-10 2019-04-02 International Business Machines Corporation Method of proactive object transferring management
US10298690B2 (en) 2017-01-10 2019-05-21 International Business Machines Corporation Method of proactive object transferring management

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5958006A (en) * 1995-11-13 1999-09-28 Motorola, Inc. Method and apparatus for communicating summarized data
US6088588A (en) * 1997-03-25 2000-07-11 Nortel Networks Corporation Method and wireless terminal for monitoring communications and providing network with terminal operation information
US20040203684A1 (en) * 2002-09-30 2004-10-14 Nokia Corporation Terminal, device and methods for a communication network
US7185360B1 (en) * 2000-08-01 2007-02-27 Hereuare Communications, Inc. System for distributed network authentication and access control

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6088591A (en) * 1996-06-28 2000-07-11 Aironet Wireless Communications, Inc. Cellular system hand-off protocol
US5999526A (en) * 1996-11-26 1999-12-07 Lucent Technologies Inc. Method and apparatus for delivering data from an information provider using the public switched network
US6332154B2 (en) 1998-09-11 2001-12-18 Genesys Telecommunications Laboratories, Inc. Method and apparatus for providing media-independent self-help modules within a multimedia communication-center customer interface
CA2296213C (en) * 2000-01-07 2009-04-14 Sedona Networks Corporation Distributed subscriber management
US20040003266A1 (en) * 2000-09-22 2004-01-01 Patchlink Corporation Non-invasive automatic offsite patch fingerprinting and updating system and method
JP3419391B2 (ja) * 2000-10-05 2003-06-23 日本電気株式会社 認証拒否端末に対し特定条件でアクセスを許容するｌａｎ
US7159031B1 (en) * 2001-01-26 2007-01-02 Fortinet, Inc. Remote customer management of virtual routers allocated to the customer
US6996393B2 (en) * 2001-08-31 2006-02-07 Nokia Corporation Mobile content delivery system
US20030208602A1 (en) * 2002-04-08 2003-11-06 Cisco Technology, Inc. System and method for pushing data in an internet protocol network environment
US7401133B2 (en) * 2002-04-23 2008-07-15 Secure Resolutions, Inc. Software administration in an application service provider scenario via configuration directives
US6832259B2 (en) * 2002-08-29 2004-12-14 Motorola, Inc. Dynamic adjustment of transmitted data size for a subscriber device
US20050177515A1 (en) * 2004-02-06 2005-08-11 Tatara Systems, Inc. Wi-Fi service delivery platform for retail service providers

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5958006A (en) * 1995-11-13 1999-09-28 Motorola, Inc. Method and apparatus for communicating summarized data
US6088588A (en) * 1997-03-25 2000-07-11 Nortel Networks Corporation Method and wireless terminal for monitoring communications and providing network with terminal operation information
US7185360B1 (en) * 2000-08-01 2007-02-27 Hereuare Communications, Inc. System for distributed network authentication and access control
US20040203684A1 (en) * 2002-09-30 2004-10-14 Nokia Corporation Terminal, device and methods for a communication network

Cited By (48)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060002350A1 (en) * 2004-07-02 2006-01-05 Cyrus Behroozi Access point control of client roaming
US7450552B2 (en) * 2004-07-02 2008-11-11 Tropos Networks, Inc. Access point control of client roaming
US20060018328A1 (en) * 2004-07-23 2006-01-26 Comcast Cable Holdings, Llc Method and system for powerline networking
US20100094997A1 (en) * 2005-06-23 2010-04-15 Joey Chou Event logging techniques for broadband wireless access networks
US7668905B2 (en) * 2005-09-07 2010-02-23 International Business Machines Corporation Method, system and computer program for providing web pages based on client state
US20070055725A1 (en) * 2005-09-07 2007-03-08 Gianluca Bernardini Method, system and computer program for providing web pages based on client state
US8494487B2 (en) * 2006-03-10 2013-07-23 Samsung Electronics Co., Ltd. Method and apparatus for authenticating mobile terminal on handover
US20070213033A1 (en) * 2006-03-10 2007-09-13 Samsung Electronics Co., Ltd. Method and apparatus for authenticating mobile terminal on handover
US10291787B2 (en) 2006-04-12 2019-05-14 Fon Wireless Limited Unified network of Wi-Fi access points
US8306502B2 (en) 2006-04-12 2012-11-06 Fon Wireless Limited System and method for linking existing Wi-Fi access points into a single unified network
US20110158215A1 (en) * 2006-04-12 2011-06-30 Fon Wireless Limited System and method for linking existing wi-fi access points into a single unified network
US7924780B2 (en) * 2006-04-12 2011-04-12 Fon Wireless Limited System and method for linking existing Wi-Fi access points into a single unified network
US9826102B2 (en) 2006-04-12 2017-11-21 Fon Wireless Limited Linking existing Wi-Fi access points into unified network for VoIP
US9088955B2 (en) 2006-04-12 2015-07-21 Fon Wireless Limited System and method for linking existing Wi-Fi access points into a single unified network
US20110182263A1 (en) * 2006-04-12 2011-07-28 Fon Wireless Limited System and method for linking existing wi-fi access points into a single unified network
US7995993B1 (en) 2006-04-12 2011-08-09 Fon Wireless Limited System and method for linking existing Wi-Fi access points into a single unified network
US8126430B2 (en) 2006-04-12 2012-02-28 Fon Wireless Limited System and method for linking existing Wi-Fi access points into a single unified network
US9125170B2 (en) 2006-04-12 2015-09-01 Fon Wireless Limited Linking existing Wi-Fi access points into unified network
US10728396B2 (en) 2006-04-12 2020-07-28 Fon Wireless Limited Unified network of Wi-Fi access points
US20070242657A1 (en) * 2006-04-12 2007-10-18 Waisman-Diamond Martin V System and method for linking existing WI-FI access points into a single unified network
US9913303B2 (en) 2006-09-06 2018-03-06 Devicescape Software, Inc. Systems and methods for network curation
US9432920B2 (en) 2006-09-06 2016-08-30 Devicescape Software, Inc. Systems and methods for network curation
US9326138B2 (en) 2006-09-06 2016-04-26 Devicescape Software, Inc. Systems and methods for determining location over a network
US20080130601A1 (en) * 2006-12-01 2008-06-05 Electronics And Telecommunications Research Institute Method for providing network communication service with constant quality regardless of being in wired or wireless network environment
US20090064306A1 (en) * 2007-08-27 2009-03-05 Microsoft Corporation Network access control based on program state
US8590012B2 (en) * 2007-08-27 2013-11-19 Microsoft Corporation Network access control based on program state
US20100263022A1 (en) * 2008-10-13 2010-10-14 Devicescape Software, Inc. Systems and Methods for Enhanced Smartclient Support
US20110087958A1 (en) * 2009-10-14 2011-04-14 Dumitru Dan Mihai Method for extracting document data from multiple sources for display on a communication device
US9418169B2 (en) * 2009-10-14 2016-08-16 Blackberry Limited Extracting document data from multiple sources for display on a mobile communication device using HTTP request headers having XML strings therein
US9015855B2 (en) 2010-12-30 2015-04-21 Fon Wireless Limited Secure tunneling platform system and method
US8910300B2 (en) 2010-12-30 2014-12-09 Fon Wireless Limited Secure tunneling platform system and method
US8955078B2 (en) * 2011-06-30 2015-02-10 Cable Television Laboratories, Inc. Zero sign-on authentication
US11178130B2 (en) 2011-06-30 2021-11-16 Cable Television Laboratories, Inc. Zero sign-on authentication
US20130007868A1 (en) * 2011-06-30 2013-01-03 Cable Television Laboratories, Inc. Zero sign-on authentication
US9961067B2 (en) 2011-06-30 2018-05-01 Cable Television Laboratories, Inc. Zero sign-on authentication
US8495714B2 (en) 2011-07-20 2013-07-23 Bridgewater Systems Corp. Systems and methods for authenticating users accessing unsecured wifi access points
US9397899B2 (en) 2012-09-26 2016-07-19 Intel Corporation Techniques for fractional wireless broadband usage
WO2014051774A1 (en) * 2012-09-26 2014-04-03 Intel Corporation Techniques for fractional wireless broadband usage
US9680872B1 (en) 2014-03-25 2017-06-13 Amazon Technologies, Inc. Trusted-code generated requests
US10511633B2 (en) 2014-03-25 2019-12-17 Amazon Technologies, Inc. Trusted-code generated requests
US10666684B2 (en) 2014-03-25 2020-05-26 Amazon Technologies, Inc. Security policies with probabilistic actions
US9854001B1 (en) * 2014-03-25 2017-12-26 Amazon Technologies, Inc. Transparent policies
US11489874B2 (en) 2014-03-25 2022-11-01 Amazon Technologies, Inc. Trusted-code generated requests
US11870816B1 (en) 2014-03-25 2024-01-09 Amazon Technologies, Inc. Trusted-code generated requests
US10020951B2 (en) * 2014-09-17 2018-07-10 Ca, Inc. Crowdsourcing-based detection, identification, and tracking of electronic devices
US20160080486A1 (en) * 2014-09-17 2016-03-17 Ca, Inc. Crowdsourcing-based detection, identification, and tracking of electronic devices
US20220361109A1 (en) * 2021-05-10 2022-11-10 Microsoft Technology Licensing, Llc System and method for reducing power consumption
US11979835B2 (en) * 2021-05-10 2024-05-07 Microsoft Technology Licensing, Llc System and method for reducing power consumption

Also Published As

Publication number Publication date
WO2005094463A2 (en) 2005-10-13
WO2005094464A3 (en) 2005-11-17
KR20060135910A (ko) 2006-12-29
EP1761866A4 (de) 2008-06-18
US8325625B2 (en) 2012-12-04
KR20070007155A (ko) 2007-01-12
EP1761866A2 (de) 2007-03-14
EP1741036A2 (de) 2007-01-10
WO2005094464A2 (en) 2005-10-13
US20060047830A1 (en) 2006-03-02
WO2005094463A3 (en) 2008-08-14

Similar Documents

Publication Publication Date Title
US20060041931A1 (en) Service level assurance system and method for wired and wireless broadband networks
US20050177515A1 (en) Wi-Fi service delivery platform for retail service providers
US10447533B2 (en) System and method for managing access point functionality and configuration
US8200773B2 (en) Client-side network access policies and management applications
US8234381B1 (en) Method and apparatus for accessing networks by a mobile device
US9398010B1 (en) Provisioning layer two network access for mobile devices
US20060174127A1 (en) Network access server (NAS) discovery and associated automated authentication in heterogenous public hotspot networks
US8130635B2 (en) Network access nodes
US8111631B2 (en) Systems and methods for automatic configuration of customer premises equipments
US20070147324A1 (en) System and method for improved WiFi/WiMax retail installation management
US8571222B1 (en) System and method for wide area wireless connectivity to the internet
US20060072583A1 (en) Systems and methods for monitoring and displaying performance metrics
WO2005076930A2 (en) Wi-fi service delivery platform for wholesale service providers
EP1969800A1 (de) Unterstützung für integrierte wlan-hotspot-clients
US20050068912A1 (en) Method and system for wirelessly providing an update to a network appliance
Cisco Configuring Accounting
CN1957347A (zh) 用于网络连接设备上的自动数据传送的方法和系统
CN116471590A (zh) 终端接入方法、装置及鉴权服务功能网元
CN101379475A (zh) 服务水平保障系统及用于有线和无线宽带网络的方法
CN116830531A (zh) 漫游期间经由基于联盟的网络提供安全服务
Ravi Design and implementation of an SDN based authentication and separation mechanism for WiFi users

Legal Events

Date Code Title Description
AS Assignment

Owner name: PCTEL, INC., ILLINOIS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BOXALL, ROBERT;SAMSALOVIC, VOJISLAV;NAIR, BIJU;REEL/FRAME:016950/0623

Effective date: 20051007

AS Assignment

Owner name: PCTEL, INC., ILLINOIS

Free format text: CORRECTIVE COVERSHEET TO CORRECT ASSIGNMENT PREVIOUSLY RECORDED ON REEL 016950, FRAME 0623.;ASSIGNORS:BOXALL, ROBERT;SAMSALOVIC, VOJISLAV;NAIR, BIJU;REEL/FRAME:017751/0043

Effective date: 20051007

AS Assignment

Owner name: SMITH MICRO SOFTWARE, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PCTEL, INC.;REEL/FRAME:020548/0803

Effective date: 20080104

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION