US20160165480A1 - Quality of Service to Over the Top Applications Used with VPN - Google Patents
Quality of Service to Over the Top Applications Used with VPN Download PDFInfo
- Publication number
- US20160165480A1 US20160165480A1 US15/042,203 US201615042203A US2016165480A1 US 20160165480 A1 US20160165480 A1 US 20160165480A1 US 201615042203 A US201615042203 A US 201615042203A US 2016165480 A1 US2016165480 A1 US 2016165480A1
- Authority
- US
- United States
- Prior art keywords
- service
- qos
- quality
- vpn
- over
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0226—Traffic management, e.g. flow control or congestion control based on location or mobility
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- 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/46—Interconnection of networks
- H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
-
- 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/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5003—Managing SLA; Interaction between SLA and QoS
- H04L41/5019—Ensuring fulfilment of SLA
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
- H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2475—Traffic characterised by specific attributes, e.g. priority or QoS for supporting traffic characterised by the type of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/66—Policy and charging system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0894—Policy-based network configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/50—Service provisioning or reconfiguring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
Definitions
- the present invention is a continuation-in-part of U.S. application Ser. No. 14/032,913, filed Sep. 20, 2013, entitled “Mechanisms For Quality of Service to Over the Top Applications For Use in Commercial Wireless Networks”; which claims priority from U.S. Provisional No. 61/714,944, filed Oct. 17, 2012, entitled “Mechanisms for Quality of Service to Over the Top Applications For Use In Commercial Wireless Networks”.
- the present application also claims priority from U.S. Provisional No. 61/815,976, filed Apr. 25, 2013, entitled “Quality of Service to Over the Top Applications Used with VPN”; and from U.S. Provisional No. 61/829,745, filed May 31, 2013, entitled “Quality of Service to Over the Top Applications Used with VPN”.
- the entirety of all four of these applications are expressly incorporated herein by reference.
- This invention relates generally to Quality of Service (QoS) control for Virtual Private Network(s) (VPNs) established between smart phones and private networks (e.g., enterprise or agency intranet) over Long Term Evolution (LTE) commercial wireless networks.
- VPNs Virtual Private Network(s)
- private networks e.g., enterprise or agency intranet
- LTE Long Term Evolution
- LTE 4G wireless broadband technology is a recent technology that supports a fast and efficient all-Internet Protocol (IP) network (i.e., a network that provides services, e.g., voice, video, data, messaging, etc., solely over the Internet). It is expected that the majority of commercial service providers will also adopt an all-Internet Protocol (IP) network at some time in the near future.
- IP all-Internet Protocol
- An over-the-top (OTT) application is an application that uses a data channel provided by an Internet service provider (ISP) to connect to the Internet instead of using any special data handling features or network services offered thereby.
- ISP Internet service provider
- over-the-top (OTT) application data is sometimes routed over a commercial wireless network via a virtual private network (VPN) tunnel (which involves the tunneling of original IP packets inside outer IP packets in an encrypted fashion).
- VPN virtual private network
- a virtual private network (VPN) tunnel provides additional transmission security to over-the-top (OTT) application data, which is especially helpful to over-the-top (OTT) applications that lack end-to-end encryption on their network connections.
- Quality of service refers to a set of performance characteristics by which a commercial wireless network is expected to convey data traffic to and from a client (quality of service (QoS) control mechanisms are applied to both the wireless and wireline components of a commercial network).
- Specific performance characteristics may include throughput (i.e. data quantity transmitted per unit time), latency (i.e. time delay between transmission and receipt of data), loss rate (i.e. frequency by which a commercial wireless network fails to deliver portions of transmitted data), jitter (i.e. a measure of variance of other characteristics), etc.
- the maximum throughput that a commercial wireless network is able to provide across all clients is dependant on: a spectrum allocation held by the commercial wireless network, a backhaul infrastructure setup between cellular towers and fixed infrastructure within the commercial wireless network, the number of cellular towers in use within the commercial wireless network, the size of a footprint assigned to each cellular tower in use within the commercial wireless network, and any sources of electromagnetic interference within the commercial wireless network.
- applications e.g. smart phone applications
- QoS quality of service
- a commercial wireless network may agree (in exchange for monetary compensation) to provide a minimum of 12 kilobit/second throughput and a minimum of 0.1 second latency to a client user equipment (UE) that desires to receive real-time streaming video feed over that wireless network.
- UE client user equipment
- a network operator may delay transmitting data for one low-level quality of service (QoS) client to prioritize data transmission for another high-level quality of service (QoS) client.
- QoS quality of service
- a network operator may discard data packets transmitted to/from one low-level quality of service (QoS) client more frequently, to ensure data conveyance for another high-level quality of service (QoS) client.
- over-the-top (OTT) applications and associated data do not typically enter into contractual quality of service (QoS) agreements with commercial wireless networks (e.g. Long Term Evolution (LTE) networks). Therefore, over-the-top (OTT) applications are typically unable to benefit from quality of service (QoS) control mechanisms (e.g, priority, packet delay, guaranteed bit rate, etc.) available thereon. Instead, most over-the-top (OTT) applications (e.g., Skype, Netflix, etc.) provide services on a best-effort basis (i.e., data delivery, efficiency not guaranteed).
- QoS quality of service
- DiffServ Differentiated Services
- IP Internet Protocol
- QoS quality of service
- DiffSery uses a 6 bit field (i.e. a DS field) in an IP header for packet classification purposes.
- a DS field may be influenced (set) by an application generating IP packets.
- a virtual private network (VPN) client may copy a DiffSery header from an incoming application IP packet (that will eventually be encapsulated) to an IP header of a tunneling IP packet to extend DiffSery quality of service (QoS) treatment to a virtual private network (VPN) environment.
- QoS quality of service
- IP Internet Protocol
- LTE long term evolution
- QoS quality of service
- OTT over-the-top
- OTT over-the-top
- VPN virtual private network
- a method and apparatus for extending conventional quality of service (QoS) treatment to over-the-top (OTT) applications transmitting data over a commercial wireless network via a virtual private network (VPN) tunnel comprises a quality of service (QoS) server.
- QoS quality of service
- an over-the-top (OTT) application server and a virtual private network (VPN) client/server routing data to/from the over-the-top (OTT) application server over a virtual private network (VPN) tunnel are each integrated with a quality of service (QoS) server.
- the over-the-top (OTT) application server and/or the virtual private network (VPN) client/server may request and get desired quality of service (QoS) treatment for application data routed by the over-the-top (OTT) application over the virtual private network (VPN) tunnel.
- QoS quality of service
- the present invention is applicable to both single-tenant virtual private network (VPN) tunnels and multi-tenant virtual private network (VPN) tunnels.
- a single-tenant virtual private network (VPN) tunnel i.e. a virtual private network (VPN) tunnel that is treated as a single application
- QoS quality of service
- a quality of service (QoS) designation requested for/by an application routing data over a single-tenant virtual private network (VPN) tunnel is applied to all application data routed over that virtual private network (VPN) tunnel.
- a multi-tenant virtual private network (VPN) tunnel may define a default quality of service (QoS) designation for application data routed to/from applications that have not indicated a preferred quality of service (QoS) designation.
- the quality of service (QoS) server forwards desired quality of service (QoS) rules embedded in a quality of service (QoS) request message to a policy and charging rules function (PCRF) on a requesting over-the-top (OTT) application/virtual private network (VPN) client devices' home mobile network operator (MNO).
- OTT over-the-top
- VPN virtual private network
- PCRF policy and charging rules function
- a connection between a quality of service (QoS) server and a policy and charging rules function (PCRF) is preferably established via a diameter Rx interface.
- QoS quality of service
- PCRF policy and charging rules function
- an over-the-top (OTT) application must provide identification details and register services and application characteristics with the quality of service (QoS) server before that application is permitted to request quality of service (QoS) treatment therefrom.
- QoS quality of service
- an over-the-top (OTT) application is required to provision one or more quality of service (QoS) application profiles, each indicating a desired level of quality of service (QoS).
- a virtual private network (VPN) client/server must furnish relevant tunneling information to the quality of service (QoS) server before that virtual private network (VPN) client/server is permitted to request quality of service (QoS) treatment therefrom.
- Relevant tunneling information varies depending upon a type of virtual private network (VPN) tunnel established.
- a single-tenant virtual private network (VPN) tunnel is required to provision identification details and one or more quality of service (QoS) application profiles on the quality of service (QoS) server.
- a multi-tenant virtual private network (VPN) tunnel must provision identification details and adequate tunneling information on the quality of service (QoS) server, but need not preprovision any quality of service (QoS) application profiles.
- Tunneling information furnished to the quality of service (QoS) server for a multi-tenant virtual private network (VPN) tunnel must enable the quality of service (QoS) to identify IP packets associated with application data routed thereover.
- a quality of service (QoS) application profile ID identifying a particular quality of service (QoS) application profile i.e. quality of service (QoS) rules
- QoS quality of service
- a quality of service (QoS) application profile ID indicates to the quality of service (QoS) server a particular quality of service (QoS) application profile to invoke.
- an over-the-top (OTT) application server detects a termination of signaling or service on an over-the-top (OTT) application client device
- the over-the-top (OTT) application server sends a quality of service (QoS) termination message to the quality of service (QoS) server, to indicate that reserved quality of service (QoS) values may be terminated on the client devices' home mobile network operator (MNO).
- QoS quality of service
- a virtual private network (VPN) client/server must inform the quality of service (QoS) server when a virtual private network (VPN) tunnel has terminated.
- QoS quality of service
- FIG. 1 depicts an exemplary network structure for extending conventional quality of service (QoS) treatment to over-the-top (OTT) applications routing data over a commercial wireless network via a virtual private network (VPN) tunnel, in accordance with the principles of the present invention.
- QoS quality of service
- OTT over-the-top
- VPN virtual private network
- FIG. 2 depicts an exemplary quality of service (QoS) server architecture, in accordance with the principles of the present invention.
- QoS quality of service
- FIG. 3 depicts an exemplary process flow for extending quality of service (QoS) treatment to over-the-top (OTT) applications routing data over a commercial wireless network via a virtual private network (VPN) tunnel, in accordance with the principles of the present invention.
- QoS quality of service
- OTT over-the-top
- VPN virtual private network
- FIG. 4 depicts conventional encryption and encapsulation of an original IP packet, in accordance with conventional IPSec virtual private network (VPN) technology.
- VPN virtual private network
- FIG. 5 depicts a conventional single-tenant virtual private network (VPN) tunnel.
- VPN virtual private network
- FIG. 6 depicts a conventional multi-tenant virtual private network (VPN) tunnel.
- VPN virtual private network
- the present invention extends conventional quality of service (QoS) treatment to over-the-top (OTT) applications transmitting data over a commercial wireless network (e.g. a long term evolution (LTE) network) via a virtual private network (VPN) tunnel.
- QoS quality of service
- OTT over-the-top
- a commercial wireless network e.g. a long term evolution (LTE) network
- LTE long term evolution
- VPN virtual private network
- New wireless standards such as long term evolution (LTE)
- LTE long term evolution
- IMS internet multimedia system
- a policy and charging rules function is a network element (in a long term evolution (LTE) packet core) that may be accessed by carrier-hosted application frameworks (e.g. IMS) (via a diameter protocol based interface (Rx)) for the purposes of providing quality of service (QoS) treatment to applications.
- LTE long term evolution
- Rx diameter protocol based interface
- over-the-top (OTT) applications are an application that provides services/content to a client user equipment (UE) over the Internet, absent the involvement of an Internet service provider (ISP).
- ISP Internet service provider
- conventional over-the-top (OTT) applications are not facilitated via carrier-hosted application frameworks, and are thus not able to benefit from quality of service (QoS) treatment available on today's commercial wireless networks.
- conventional over-the-top (OTT) applications are typically forced to operate on a best-effort basis (i.e. data delivery, efficiency not guaranteed).
- over-the-top (OTT) applications are expected to become increasingly common.
- LTE long term evolution
- OTT over-the-top
- mission critical applications such as those applications used by emergency dispatch personnel and emergency first responders
- OTT over-the-top
- the present invention expands a method of extending conventional quality of service (QoS) treatment to over-the-top (OTT) applications routing data over a commercial wireless network, as disclosed in co-pending and co-owned U.S. patent application Ser. No. 14/032,913, filed Sep. 20, 2013, entitled: “MECHANISMS FOR QUALITY OF SERVICE TO OVER THE TOP APPLICATIONS FOR USE IN COMMERCIAL WIRELESS NETWORKS”, claiming priority from U.S. Provisional Application No. 61/703,554, filed Sep. 20, 2012, entitled: “MECHANISMS FOR QUALITY OF SERVICE TO OVER THE TOP APPLICATIONS FOR USE IN COMMERCIAL WIRELESS NETWORKS”, and from U.S. Provisional No.
- the present invention addresses a variation of the scenario described in U.S. application Ser. No. 14/032,913.
- the present invention addresses a scenario wherein an over-the-top (OTT) application client on a user equipment (UE) is connected to a cloud based over-the-top (OTT) application server via a virtual private network (VPN) connection.
- a conventional virtual private network (VPN) connection provides additional transport security to over-the-top (OTT) application data traversing a commercial wireless network, by tunneling original IP packets inside outer IP packets in an encrypted fashion.
- Mechanisms for establishing a virtual private network (VPN) tunnel appropriate to convey over-the-top (OTT) application data are well known to those skilled in the art.
- OTT over-the-top
- OTT over-the-top
- MNO mobile network operators
- the present invention extends conventional quality of service (QoS) treatment to virtual private networks (VPN) carrying over-the-top (OTT) application data without burdening virtual private networks (VPN) with network integration aspects, such as: knowledge of user location, knowledge of a policy and charging rules function (PCRF), knowledge of a long term evolution (LTE) packet core, etc.
- QoS quality of service
- VPN virtual private networks
- OTT over-the-top
- PCRF policy and charging rules function
- LTE long term evolution
- an over-the-top (OTT) application server and a virtual private network (VPN) client/server carrying data to/from that over-the-top (OTT) application server over a virtual private network (VPN) tunnel are each integrated with an inventive quality of service (QoS) server.
- QoS quality of service
- the over-the-top (OTT) application server and/or the virtual private network (VPN) client/server may send a quality of service (QoS) request message to the inventive quality of service (QoS) server (via an appropriate virtual private network (VPN) client/server interface or over-the-top (OTT) application interface) to request that desired quality of service (QoS) treatment (identified by a quality of service (QoS) application profile ID) be applied to application data routed by the over-the-top (OTT) application over the virtual private network (VPN) tunnel.
- QoS quality of service
- the inventive quality of service (QoS) server forwards quality of service (QoS) rules embedded in a quality of service (QoS) request message to a policy and charging rules function (PCRF) residing on a requesting over-the-top (OTT) application/virtual private network (VPN) client devices' home mobile network operator (MNO). If the client device is roaming, then the policy and charging rules function (PCRF) on that device's home mobile network operator (MNO) forwards quality of service (QoS) rules to a policy and charging rules function (PCRF) serving the client device. Quality of service (QoS) treatment is then carried out by the policy and charging rules function (PCRF) in a conventional manner.
- OTT over-the-top
- VPN virtual private network
- an over-the-top (OTT) application server and/or a virtual private network (VPN) client/server may modify a previously requested level of quality of service (QoS) treatment, when a previously requested level of quality of service (QoS) treatment is not resulting in desired performance.
- QoS quality of service
- the inventive solution may be applied to various virtual private network (VPN) technologies, including: a layer 2 tunneling protocol (L2TP) technology, a point-to-point tunneling protocol (PPTP) technology, a transport layer security/virtual private network (VPN) technology, etc.
- L2TP layer 2 tunneling protocol
- PPTP point-to-point tunneling protocol
- VPN transport layer security/virtual private network
- the present invention is described herein via use of an IPSec virtual private network (VPN) technology configured in tunnel mode.
- IPSec virtual private network (VPN) technology all IP datagrams (including both datagram header and datagram packet) routed over a virtual private network (VPN) tunnel are first encapsulated inside new IP datagrams with IPSec headers.
- FIG. 4 depicts conventional encryption and encapsulation of an original IP packet, in accordance with conventional IPSec virtual private network (VPN) technology.
- VPN virtual private network
- an original IP packet 420 (including an original IP header 440 and an original application payload 450 ) is encrypted 400 a , 400 b and encapsulated in an outer IP packet 410 with an IPSec header 430 before it is routed over a conventional IPSec virtual private network (VPN) tunnel.
- a virtual private network (VPN) client/server also interprets an original IP packet 420 and assigns an appropriate security parameter index (SPI) value (in accordance with a preconfigured security parameter index (SPI) value) thereto before routing the IP packet over a virtual private network (VPN) tunnel.
- SPI security parameter index
- a security parameter index (SPI) value serves as an index to a conventional security association database (SADB) (i.e.
- SADB a database that maintains information for a virtual private network (VPN) tunnel) maintained for a virtual private network (VPN) tunnel.
- a security association database preferably includes some or all of the following information: security association information (i.e. security parameter index, IPSec protocol, IP destination address) and security policy information (i.e. IP source address, IP destination address, fully qualified domain name, source port number, destination port number, quality of service (QoS) application profile ID).
- the present invention is applicable to both single-tenant virtual private network (VPN) tunnels and multi-tenant virtual private network (VPN) tunnels.
- VPN virtual private network
- VPN multi-tenant virtual private network
- FIG. 5 depicts a conventional single-tenant virtual private network (VPN) tunnel.
- VPN virtual private network
- a single-tenant virtual private network (VPN) tunnel 500 is always treated as a single application, regardless of how many applications 510 actually utilize the tunnel 500 . Therefore, a single-tenant virtual private network (VPN) tunnel 500 is only permitted one quality of service (QoS) designation 540 at a time.
- QoS quality of service
- a quality of service (QoS) designation requested for/by an application routing data over a single-tenant virtual private network (VPN) tunnel 500 is applied to all application data 510 routed over that virtual private network (VPN) tunnel 500 .
- FIG. 6 depicts a conventional multi-tenant virtual private network (VPN) tunnel.
- VPN virtual private network
- applications 530 transmitting data over a multi-tenant virtual private network (VPN) tunnel 520 are acknowledged independently and may thus be assigned their own individual quality of service (QoS) designations 550 .
- QoS quality of service
- a quality of service (QoS) designation 550 requested for/by an application routing data over a multi-tenant virtual private network (VPN) tunnel 500 is only applied to application data routed by that application.
- FIG. 1 depicts an exemplary network structure for extending conventional quality of service (QoS) treatment to over-the-top (OTT) applications routing data over a commercial wireless network via a virtual private network (VPN) tunnel, in accordance with the principles of the present invention.
- QoS quality of service
- OTT over-the-top
- VPN virtual private network
- a quality of service (QoS) server 100 is configured to directly interface with one or more commercial wireless networks 102 a , 102 b via a conventional policy and charging rules function (PCRF) (i.e. an IP multimedia subsystem (IMS)/long term evolution (LTE) network component) 104 .
- PCRF policy and charging rules function
- IMS IP multimedia subsystem
- LTE long term evolution
- a connection between a quality of service (QoS) server 100 and a policy and charging rules function (PCRF) 104 is preferably established via a diameter Rx interface 106 (3GPP specifications 29.209, 29.214).
- the primary function of a quality of service (QoS) server 100 is to translate diameter protocol interface 106 messages to other communication mediums and vice versa.
- the inventive quality of service (QoS) server 100 takes on the role of a special application function (AF) connected on the backend (i.e. not accessible to a user) 110 of one or more disparate applications.
- the quality of service (QoS) server 100 also establishes a connection with a virtual private network (VPN) server 112 and/or virtual private network (VPN) client 118 , when application data exchanged between an over-the-top (OTT) application client 120 and an over-the-top (OTT) application server 110 happens over a virtual private network (VPN) tunnel 114 .
- VPN virtual private network
- OTT over-the-top
- OTT over-the-top
- the inventive quality of service (QoS) server 100 uses a secure virtual private network (VPN) client/server interface 116 to interface with a virtual private network (VPN) client 118 /server 112 on either end of a virtual private network (VPN) tunnel 114 .
- virtual private network (VPN) clients 118 /servers 112 use the virtual private network (VPN) client/server interface 116 to provide relevant tunneling information to the quality of service (QoS) server 100 .
- Relevant tunneling information enables the quality of service (QoS) server 100 to identify IP packets associated with over-the-top (OTT) application data transmitted over a virtual private network (VPN) tunnel 114 .
- OTT over-the-top
- a virtual private network (VPN) tunnel 114 is established between a virtual private network (VPN) client 118 on a user equipment 108 , and a fixed infrastructure virtual private network (VPN) server 112 , so that data traffic transmitted to/from one or more over-the-top (OTT) application clients 120 on the user equipment (UE) 108 may traverse the virtual private network (VPN) tunnel 114 .
- a virtual private network (VPN) tunnel 114 encrypts and encapsulates an original IP packet inside an outer IP packet while the IP packet is traversing a commercial wireless network.
- An underlying commercial wireless network 102 a , 102 b is typically configured to provide a certain level of quality of service (QoS) treatment to traffic traversing a virtual private network (VPN) tunnel 114 .
- QoS quality of service
- the quality of service (QoS) server 100 must be able to communicate with backend applications 110 , carrier policy and charging rules (PCRF) function(s) 104 , and virtual private network (VPN) clients 118 /servers 112 , simultaneously. Simultaneous communication may be permitted via a firewall setting and/or other network configuration rules.
- PCRF carrier policy and charging rules
- VPN virtual private network
- a quality of service (QoS) server 100 may be located separate from a mobile network operator (MNO) 102 a , 102 b or co-located with a mobile network operator (MNO) 102 a , 102 b .
- MNO mobile network operator
- Possible mobile network operator (MNO) integration targets currently include: a universal mobile telecommunications system (UMTS), long term evolution (LTE) technology, an evolved-universal mobile telecommunications system (E-UMTS), long term evolution (LTE) technology advanced, and Wi-Fi.
- UMTS universal mobile telecommunications system
- LTE long term evolution
- E-UMTS evolved-universal mobile telecommunications system
- LTE long term evolution
- Wi-Fi Wi-Fi
- FIG. 2 depicts an exemplary quality of service (QoS) server architecture, in accordance with the principles of the present invention.
- QoS quality of service
- the inventive quality of service (QoS) server 100 interacts with a mobile network operator (MNO) policy and charging rules function (PCRF) interface (a diameter protocol interface) 106 , an over-the-top (OTT) application interface 210 , a number portability database (NPDB) interface 240 , and a virtual private network (VPN) client/server interface 116 to extend quality of service (QoS) treatment to applications routing data over a commercial wireless network 102 a , 102 b via a virtual private network (VPN) tunnel 114 .
- MNO mobile network operator
- PCRF policy and charging rules function
- OTT over-the-top
- NPDB number portability database
- VPN virtual private network
- the quality of service (QoS) server 100 maintains profiles and information for over-the-top (OTT) applications in a local application information database 220 , tunneling and IP packet information for registered virtual private network (VPN) tunnels in a local virtual private network (VPN) tunneling information database 250 , and home mobile network operator (MNO) information for over-the-top (OTT) application client devices in a local mobile network operator (MNO) information database 230 .
- OTT over-the-top
- MNO home mobile network operator
- the quality of service (QoS) server 100 accesses a number portability database (NPDB) interface 240 to retrieve relevant home mobile network operator (MNO) information from an external number portability database (NPDB) 270 .
- NPDB number portability database
- the over-the-top (OTT) application interface 210 is designed to operate over a secure, transport layer security (TLS)/secure sockets layer (SSL) communications channel that utilizes representational state transfer (REST) hypertext transfer protocol (HTTP), hypertext transfer protocol (HTTP), simple object access protocol (SOAP), extensible markup language (XML), etc., message formats.
- TLS transport layer security
- SSL secure sockets layer
- REST representational state transfer
- HTTP hypertext transfer protocol
- HTTP hypertext transfer protocol
- HTTP hypertext transfer protocol
- SOAP simple object access protocol
- XML extensible markup language
- New mediums for the over-the-top (OTT) application interface 210 may be defined and used, as appropriate, as long as application quality of service (QoS) message formats (i.e. attributes and corresponding values included in application quality of service messages) conform minimally to application quality of service (QoS) message formats described herein (i.e.
- the quality of service (QoS) server 100 uses a diameter Rx protocol (3GPP 29.214) to interface 106 with a mobile network operator (MNO) policy and charging rules function (PCRF) 104 .
- MNO mobile network operator
- PCRF policy and charging rules function
- a mobile network operator (MNO) policy and charging rules function (PCRF) interface 106 provides discovery and addressing of a home policy and charging rules function (HPCRF) 104 assigned to a requesting over-the-top (OTT) application/virtual private network (VPN) client device 108 .
- HPCRF home policy and charging rules function
- the mobile network operator (MNO) policy and charging rules function (PCRF) interface 106 is also enhanced to allow tracking registration of the following IP header information: a virtual private network (VPN) security parameter index (SPI) (per RFC 2401, as required with IPSec protocol by a virtual private network (VPN) client/server) and an IPSec protocol (per RFC 2401).
- VPN virtual private network
- SPI security parameter index
- IPSec protocol per RFC 2401
- the quality of service (QoS) server 100 assumes the role of an application function (AF) and complies with policy and charging rules function (PCRF) 104 discovery and addressing, as described in a 3GPP series 29.213 specification.
- the quality of service (QoS) server 100 preferably maintains a table with a fully qualified domain name (FQDN) or internet protocol (IP) address of a policy and charging rules function (PCRF) 104 , for each supported single policy and charging rules function (PCRF) mobile network operator (MNO), and a diameter routing agent, for each supported multi-policy and charging rules function (PCRF) mobile network operator (MNO).
- FQDN fully qualified domain name
- IP internet protocol
- the quality of service (QoS) server 100 interfaces with a home policy and charging rules function (HPCRF) 104 , regardless as to whether or not a client user equipment (UE) 108 is roaming.
- a home policy and charging rules function (HPCRF) 104 coordinates a download of quality of service (QoS) rules to a visiting policy and charging rules function (VPCRF) in a roaming network (per 3GPP standards) when a requesting client user equipment (UE) 108 is roaming.
- number portability databases (NPDB) 270 and the local mobile network operator (MNO) information database 230 support multiple transaction capabilities application part (TCAP) based protocols (e.g., advanced intelligent network (AIN), intelligent network application protocol (INAP), American national standards institute ((ANSI)-41), etc.) for number portability queries, since such protocols support queries from both wireline and wireless networks based on various standards.
- TCAP transaction capabilities application part
- AIN advanced intelligent network
- INAP intelligent network application protocol
- ANSI American national standards institute
- the quality of service (QoS) server 100 preferably uses a number portability request (NPREQ) TCAP query (per telecommunications industry association/electronic industries association (TIA/EIA)-756A and telecommunications industry association/electronic industries association (TIA/EIA) ANSI41-D specifications) to determine a current mobile network operator (MNO) associated with an over-the-top (OTT) application client device 108 .
- NPREQ number portability request
- TCAP query per telecommunications industry association/electronic industries association (TIA/EIA)-756A and telecommunications industry association/electronic industries association (TIA/EIA) ANSI41-D specifications
- MNO mobile network operator
- OTT over-the-top
- the quality of service (QoS) server 100 may easily be extended to support other protocols for number portability lookup.
- the quality of service (QoS) server 100 uses a virtual private network (VPN) client/server interface 116 to interface with a virtual private network (VPN) client 118 and/or a virtual private network (VPN) server 112 .
- the virtual private network (VPN) client/server interface 116 is designed to operate over a secure transport layer security (TLS)/secure sockets layer (SSL) communications channel that utilizes representational state transfer (REST) hypertext transfer protocol (HTTP), hypertext transfer protocol (HTTP), simple object access protocol (SOAP), extensible markup language (XML), etc., message formats.
- the quality of service (QoS) server 100 may also/alternatively interface with a virtual private network (VPN) client 118 via a wireless network connection 260 .
- New mediums for the virtual private network (VPN) client/server interface 116 may be defined and used as appropriate, as long as VPN quality of service (QoS) message formats (i.e. attributes and corresponding values included in VPN quality of service (QoS) messages) conform minimally to VPN quality of service (QoS) message formats described herein (i.e. a VPN quality of service (QoS) request message format, a VPN quality of service (QoS) response message format, and a VPN quality of service (QoS) termination message format).
- a VPN quality of service (QoS) message may additionally be embedded in a defined message format, e.g., a radius or diameter message format.
- FIG. 3 depicts an exemplary process flow for extending quality of service (QoS) treatment to over-the-top (OTT) applications routing data over a commercial wireless network via a virtual private network (VPN) tunnel, in accordance with the principles of the present invention.
- QoS quality of service
- OTT over-the-top
- VPN virtual private network
- a virtual private network (VPN) tunnel performs VPN profile configuration with a quality of service (QoS) server 100 via an authenticated virtual private network (VPN) client/server interface 116 .
- QoS quality of service
- a virtual private network (VPN) client/server furnishes relevant tunneling information to the quality of service (QoS) server 100 for a virtual private network (VPN) tunnel established therebetween.
- Relevant tunneling information varies depending upon the type of virtual private network (VPN) tunnel established.
- a single-tenant virtual private network (VPN) tunnel 500 provisions one or more quality of service (QoS) application profiles (and corresponding quality of service application profile IDs) on the quality of service (QoS) server 100 during VPN profile configuration.
- QoS quality of service
- a quality of service (QoS) application profile includes tunnel identification details and indicates a desired level of quality of service (QoS) treatment.
- a multi-tenant virtual private network (VPN) tunnel 520 provisions identification details on the quality of service (QoS) server 100 during VPN profile configuration, but need not provision any quality of service application profiles. Rather, over-the-top (OTT) applications 530 utilizing a multi-tenant virtual private network (VPN) tunnel 520 provision their own quality of service (QoS) application profiles on the quality of service (QoS) server 100 during application profile configuration, performed in step 1 b .
- a quality of service (QoS) designation requested by an over-the-top (OTT) application transmitting data over a multi-tenant virtual private network (VPN) tunnel 520 is associated to that multi-tenant virtual private network (VPN) tunnel 520 .
- a multi-tenant virtual private network (VPN) 520 tunnel must provide adequate tunneling information (including IPSec security policy and IPSec security association information) to the quality of service (QoS) server 100 during VPN profile configuration.
- Adequate tunneling information is any information that enables the quality of service (QoS) server 100 to determine actual IP header information 440 associated with application data routed over the multi-tenant virtual private network (VPN) tunnel 520 .
- tunneling information must enable the quality of service (QoS) server 100 to adequately communicate quality of service (QoS) rules defined in a quality of service (QoS) request message to a relevant policy and charging rules function (PCRF) 104 .
- QoS quality of service
- Table 1 depicts exemplary tunneling information provided to the quality of service (QoS) server during virtual private network (VPN) profile configuration.
- QoS quality of service
- VPN virtual private network
- IPSec security policy information for encapsulated data traffic
- IPSec security association information tunnel header information relevant to a virtual private network (VPN) tunnel
- QoS quality of service
- Relevant IPSec security policy information preferably includes: an IP source address, an IP destination address, a fully qualified domain name, a source port number, a destination port number, and a quality of service application profile ID.
- Relevant IPSec security association information preferably includes: a security parameter index, an IPSec protocol, and an IP destination address.
- tunneling information must be furnished to the quality of service (QoS) server 100 for each new virtual private network (VPN) tunnel that is established.
- tunneling information may either be preprovisioned on the quality of service (QoS) server 100 during VPN profile configuration, or provided to the quality of service (QoS) server 100 dynamically, via use of a VPN quality of service (QoS) registration message.
- an application performs application profile configuration on the quality of service (QoS) server 100 via an authenticated over-the-top (OTT) application interface 210 .
- an over-the-top (OTT) application must provide identification details and register services and application characteristics with a quality of service (QoS) server 100 before that application is permitted to request quality of service (QoS) treatment therefrom.
- the quality of service (QoS) server 100 only accepts registration attempts from over-the-top (OTT) applications for which the quality of service (QoS) server 100 has been pre-configured to accept registration attempts.
- over-the-top (OTT) applications are permitted to register with a quality of service (QoS) server 100 .
- over-the-top (OTT) applications that are granted registration with a quality of service (QoS) server 100 are only permitted to receive levels of quality of service (QoS) treatment for which they have been pre-authorized to receive.
- Quality of service (QoS) requests are validated by the quality of service (QoS) server 100 before they are processed.
- An over-the-top (OTT) application also identifies service abilities and provisions one or more quality of service (QoS) application profiles on the quality of service (QoS) server 100 during application profile configuration.
- the quality of service (QoS) server 100 must first collect the following data from the over-the-top (OTT) application (more characteristics may be required as new application characteristics present themselves): an over-the-top (OTT) application identifier, over-the-top (OTT) access credentials, one or more quality of service (QoS) application profile IDs, over-the-top (OTT) application characteristics, and one or more mobile network operator (MNO) associations.
- OTT over-the-top
- MNO mobile network operator
- an over-the-top (OTT) application identifier is a unique string (synchronized with a carrier provided “AF-Application-Identifier”) that is provided to an over-the-top (OTT) application via an out-of-band mechanism.
- An over-the-top (OTT) application identifier may be prefixed with quality of service (QoS) unique identifiers for use on the quality of service (QoS) server 100 .
- QoS quality of service
- Over-the-top (OTT) access credentials e.g. a secret/password or public key infrastructure (PKI) verification
- PKI public key infrastructure
- a quality of service (QoS) application profile ID is a quality of service (QoS) specific value, defined per application identifier. More particularly, the quality of service (QoS) application profile ID is defined by the quality of service (QoS) server 100 and provided to an over-the-top (OTT) application via an out of band mechanism.
- QoS quality of service
- a quality of service (QoS) application profile ID points to a quality of service (QoS) application profile that is to be provisioned for an over-the-top (OTT) application.
- a quality of service (QoS) application profile contains application details (e.g. service characteristics, etc.) and indicates a desired level of quality of service (QoS) treatment.
- a quality of service (QoS) application profile ID is referenced in each quality of service (QoS) request message sent to the quality of service (QoS) server 100 , to indicate to the quality of service (QoS) server 100 a particular quality of service (QoS) application profile to invoke.
- an over-the-top (OTT) application may provision multiple quality of service (QoS) application profiles to indicate varying levels of desired quality of service (QoS).
- Over-the-top (OTT) application characteristics provided to the quality of service (QoS) server 100 during application profile configuration include (this list may be extended as new requirements develop, either by 3GPP specifications or via over-the-top (OTT) evolution): a media component number (i.e. an ordinal number of a media component), a media sub-component (i.e. a set of flows for one flow identifier), an application identifier, a media type (e.g.
- a media sub-component field may include the following characteristics: a flow number (i.e. an ordinal number of the IP flow), a flow description (e.g. uplink (UL) and/or downlink (DL)), a flow status, flow usage, a maximum requested bandwidth (Bw) uplink (UL), a maximum requested bandwidth (Bw) downlink (DL), and an application function (AF) signaling protocol.
- a flow number i.e. an ordinal number of the IP flow
- a flow description e.g. uplink (UL) and/or downlink (DL)
- a flow status e.g. uplink (UL) and/or downlink (DL)
- flow usage e.g. uplink (UL) and/or downlink (DL)
- Bw maximum requested bandwidth
- Bw maximum requested bandwidth
- DL maximum requested bandwidth signaling protocol
- a mobile network operator (MNO) associations field provided to the quality of service (QoS) server 100 during application profile configuration identifies all of the networks for which an over-the-top (OTT) application is authorized to designate quality of service (QoS) settings.
- Values in a mobile network operator (MNO) associations field are defined per quality of service (QoS) implementation and represent system logical identifiers for the purposes of routing communications to particular policy and charging rules (PCRF) functions.
- PCRF policy and charging rules
- an over-the-top (OTT) application provisions one or more quality of service (QoS) application profiles on the quality of service (QoS) server 100 .
- QoS quality of service
- the over-the-top (OTT) application may begin submitting registrations to the quality of service (QoS) server 100 , on a per user equipment (UE) basis.
- UE user equipment
- an over-the-top (OTT) application is required to register with the quality of service (QoS) server 100 periodically.
- an over-the-top (OTT) application may send quality of service (QoS) requests to the quality of service (QoS) server 100 , on a per user equipment (UE) basis.
- QoS quality of service
- a virtual private network (VPN) tunnel 114 is established between a virtual private network (VPN) client 118 on a user equipment (UE) 108 and a fixed infrastructure virtual private network (VPN) server 112 , so as to allow data traffic transmitted to/from one or more over-the-top (OTT) application clients 120 (that have undergone application profile configuration on the quality of service (QoS) server 100 ) on the user equipment (UE) 108 to traverse the tunnel 114 .
- OTT over-the-top
- QoS quality of service
- the virtual private network (VPN) client 118 /server 112 sends a VPN quality of service (QoS) registration message with appropriate tunneling information to the quality of service (QoS) server 100 during VPN tunnel establishment, as depicted in steps 3 a and 3 b of FIG. 3 .
- the quality of service (QoS) server 112 Upon receipt of the VPN quality of service (QoS) registration message, the quality of service (QoS) server 112 returns a VPN quality of service (QoS) registration response message to the virtual private network (VPN) client 118 /server 112 , as depicted in steps 4 a and 4 b of FIG. 3 .
- VPN tunneling information may alternatively be provisioned on the quality of service (QoS) server 100 during VPN profile configuration.
- the virtual private network (VPN) client 118 /server 112 may send a VPN quality of service (QoS) request message to the quality of service (QoS) server 100 to request desired quality of service (QoS) treatment therefrom, as shown in steps 5 a and 5 b of FIG. 3 .
- QoS VPN quality of service
- VPN quality of service (QoS) registration and request messages preferably include: a message ID (i.e. an identifier defined by, and unique to, a requesting virtual private network (VPN) server 112 /client 118 ), a quality of service (QoS) application profile ID (optional), a publically available mobile network assigned source framed internet protocol (IP) address (an attribute-value pair (AVP)) or framed IPv6 prefix (an attribute-value pair (AVP), RFC 4005 [12]), a flow description (an attribute-value pair (AVP), 3GPP 29.214), a virtual private network (VPN) security parameter index (SPI) (per RFC 2041, as required with IPSec protocol by the virtual private network (VPN) client/server), an IPSec protocol (per RFC 2041), a virtual private network (VPN) IP destination (i.e. a routable IP address for the virtual private network (VPN) server), and a
- a quality of service (QoS) application profile ID in a VPN quality of service (QoS) request message indicates a desired level of quality of service (QoS) treatment.
- a quality of service (QoS) application profile ID is required in a VPN quality of service (QoS) request message when the message is provided to the quality of service (QoS) server 100 dynamically. Otherwise, the quality of service (QoS) server 100 derives a quality of service (QoS) application profile ID based on a combination of values embedded in the VPN quality of service (QoS) request message.
- a flow description is required in a VPN quality of service (QoS) request message when a quality of service (QoS) application profile ID is not provided therein.
- a flow description must comprise one of the following two directions: ‘in’ or ‘out’, whereas direction ‘in’ refers to an uplink (UL) IP flow and direction ‘out’ refers to a downlink (DL) IP flow.
- a flow description may also contain: a source and destination IP address (possibly masked), a protocol and a source and destination port (a source port may be omitted to indicate that any source port is allowed). Lists and ranges may not be used to indicate source and/or destination ports.
- the quality of service (QoS) server 100 accepts VPN quality of service (QoS) request messages from both a virtual private network (VPN) client 118 and a virtual private network (VPN) server 112 .
- VPN virtual private network
- VPN virtual private network
- VPN virtual private network
- QoS quality of service
- OTT over-the-top
- a VPN-CS field is preferably used to provide such a reference.
- VPN quality of service (QoS) request messages are sent by both a virtual private network (VPN) server 112 and a virtual private network (VPN) client 118 for a single virtual private network (VPN) connection 114
- optional attribute tag, ‘VPN-CS’ is preferably included therein.
- Optional attribute tag ‘VPN-CS’ contains a unique message identifier that is used by both a virtual private network (VPN) server 112 and a virtual private network (VPN) client 118 , to show that messages refer to a single virtual private network (VPN) connection 114 .
- the quality of service (QoS) server 100 performs VPN quality of service (QoS) request message validation in response to a VPN quality of service (QoS) request message received thereon.
- QoS quality of service
- the quality of service (QoS) server 100 validates a quality of service (QoS) application profile ID received in the VPN quality of service (QoS) request message.
- the quality of service (QoS) server 100 may either determine a quality of service (QoS) application profile ID directly or indirectly from the VPN quality of service (QoS) request message. Indirect determination of a quality of service (QoS) application profile ID includes analyzing and matching VPN quality of service (QoS) request message parameters to an appropriate quality of service (QoS) application profile ID. Once a quality of service (QoS) application profile ID is determined, the quality of service (QoS) server 100 performs one of the following two potential courses of action, depending upon the type of virtual private network (VPN) tunnel 114 established in steps 2 a - 4 b.
- VPN virtual private network
- the quality of service (QoS) server 100 records and tracks virtual private network (VPN) 114 tunneling information received in the VPN quality of service (QoS) request message in a virtual private network (VPN) tunneling information database 250 , and subsequently returns a VPN quality of service (QoS) response message to the requesting virtual private network (VPN) client 118 /server 112 , as depicted in step 7 .
- VPN virtual private network
- the quality of service (QoS) server 100 then waits to receive an application quality of service (QoS) registration message or an application quality of service (QoS) termination message from an over-the-top (OTT) application routing or attempting to route data over the virtual private network (VPN) tunnel 114 .
- QoS application quality of service
- OTT over-the-top
- VPN virtual private network
- a quality of service (QoS) application profile ID received in an application quality of service (QoS) request message differs from a quality of service (QoS) application profile ID embedded in a VPN quality of service (QOS) request message
- QoS quality of service
- QoS quality of service
- the quality of service (QoS) server 100 immediately applies quality of service (QoS) rules received in the VPN quality of service (QoS) registration or request message to all application data routed over the virtual private network (VPN) tunnel 114 .
- QoS quality of service
- the quality of service rules are extracted from the VPN quality of service (QoS) registration message if that is the only message received and VPN quality of services (QoS) request message if both are received.
- the quality of service (QoS) server 100 queries a local mobile network operator (MNO) information database 230 to retrieve home mobile network operator (MNO) information for the over-the-top (OTT) application/virtual private network (VPN) client device 108 , as depicted in step 8 .
- MNO local mobile network operator
- the quality of service (QoS) server 100 If the quality of service (QoS) server 100 cannot find home mobile network operator (MNO) information for the client device in the local mobile network operator (MNO) information database 230 , then the quality of service (QoS) server 100 alternatively queries an external number portability database (NPDB) 270 via a number portability database (NPDB) interface 240 . Results from either the number portability database (NPDB) 270 or the local mobile network operator (MNO) information database 230 provide the quality of service (QoS) server 100 with enough information to determine a home mobile network operator (MNO) for the over-the-top (OTT) application/VPN client device 108 (step 9 ).
- MNO home mobile network operator
- OTT over-the-top
- the quality of service (QoS) server 100 uses the quality of service (QoS) application profile ID defined in the VPN quality of service (QoS) registration (or request if received) message to determine whether or not over-the-top (OTT) applications routing data over the virtual private network (VPN) tunnel are authorized to influence quality of service (QoS) treatment on the home mobile network operator (MNO) (step 10 ).
- QoS quality of service
- OTT over-the-top
- VPN virtual private network
- the quality of service (QoS) server 100 sends a diameter authentication/authorization request (AAR) message with appropriate quality of service (QoS) information to a policy and charging rules function (PCRF) 104 on the client devices' 108 home mobile network operator (MNO), as shown in step 11 .
- AAR diameter authentication/authorization request
- PCRF policy and charging rules function
- step 12 the policy and charging rules function (PCRF) 104 on the client devices' 108 home mobile network operator (MNO) receives the quality of service (QoS) information and returns a diameter authentication/authorization answer (AAA) message to the quality of service (QoS) server 100 .
- PCRF policy and charging rules function
- the quality of service (QoS) server 100 Upon receipt of the diameter authentication/authorization answer (AAA) message, the quality of service (QoS) server 100 sends a VPN quality of service (QoS) response message to the requesting VPN client 118 /server 112 , as depicted in step 13 .
- AAA diameter authentication/authorization answer
- QoS VPN quality of service
- a VPN quality of service (QoS) response message preferably includes: a message ID, an application identifier, and a status identifier.
- a status identifier included in a status field of a VPN quality of service (QoS) response message may be any one or more of the following: a success status identifier ( 100 ), a quality of service (QoS) system failure status identifier ( 200 ) (indicating a default failure or unexpected failure with no available details), a failed validation of application identifier/access credentials status identifier ( 201 ), a failed validation of quality of service (QoS) profile ID status identifier ( 202 ), a quality of service (QoS) system failure reserved message status identifier (defined per quality of service (QoS) implementation and used to explain a unique system failure) ( 203 - 299 ), a PCRF unavailable status identifier ( 300 ), and/or an AAR/AAA message failure status identifier ( 400 ), wherein
- the over-the-top (OTT) application client 120 configured to route data over the virtual private network (VPN) tunnel 114 may use the virtual private network (VPN) tunnel 114 to register with a corresponding over-the-top (OTT) application server 110 (via a Gi/SGi interface 310 ), as shown in steps 14 a and 14 b of FIG. 3 .
- the over-the-top (OTT) application server 110 may attempt to establish a mutually authenticated (client 120 and server 110 ) transport layer security (TLS)/secure sockets layer (SSL) connection with the inventive quality of service (QoS) server 100 (via standard TLS/SSL procedures for mutual authentication), as shown in step 15 .
- TLS transport layer security
- SSL secure sockets layer
- the over-the-top (OTT) application server 110 sends an application quality of service (QoS) request message to the quality of service (QoS) server 100 to request that a desired level of quality of service (QoS) treatment be applied to application data routed by that over-the-top (OTT) application over the virtual private network (VPN) tunnel 114 , as portrayed in step 16 .
- QoS application quality of service
- a quality of service (QoS) request message preferably includes: a message ID (i.e. an identifier defined by, and unique to, a requesting over-the-top (OTT) application), an application identifier (as described in 3GPP series 29.214 specification), access credentials (e.g.
- IP internet protocol
- AVP attribute-value pair
- RFC 4005 framed IPv6 prefix
- UPN service uniform resource name
- a flow description in an application quality of service (QoS) request message must comprise one of the following two directions: ‘in’ or ‘out’, whereas direction ‘in’ refers to an uplink (UL) IP flow and direction ‘out’ refers to a downlink (DL) IP flow.
- a flow description in an application quality of service (QoS) request message may also contain: a source and destination IP address (possibly masked), a protocol, and a source and destination port (a source port may be omitted to indicate that any source port is allowed). Lists and ranges may not be used to indicate source and/or destination ports.
- a quality of service (QoS) application profile ID in an application quality of service (QoS) request message indicates appropriate quality of service (QoS) information to send to a home policy and charging rules function (PCRF) 104 .
- QoS quality of service
- PCRF home policy and charging rules function
- the quality of service (QoS) server 100 performs application quality of service (QoS) request message validation in response to an application quality of service (QoS) request message received thereon, as portrayed in step 17 of FIG. 3 .
- QoS application quality of service
- the quality of service (QoS) server 100 validates the application identifier, access credentials (e.g. a secret/password public key infrastructure (PKI) verification, etc.), and quality of service (QoS) application profile ID received in the application quality of service (QoS) request message, against application profiles maintained in a local application information database 220 .
- the quality of service (QoS) server 100 validates the format and values of application quality of service (QoS) request message attributes in accordance with a 3GPP series 29.214 specification.
- the quality of service (QoS) server 100 queries a local mobile network operator (MNO) information database 230 to retrieve home mobile network operator (MNO) information for the requesting over-the-top (OTT) application client device 108 , as depicted in step 18 . If the quality of service (QoS) server 100 cannot find home mobile network operator (MNO) information for the requesting client device 108 in the local mobile network operator (MNO) information database 230 , then the quality of service (QoS) server 100 alternatively queries an external number portability database (NPDB) 270 via a number portability database (NPDB) interface 240 .
- NPDB external number portability database
- Results from either the number portability database (NPDB) 270 or the local mobile network operator (MNO) information database 230 provide the quality of service (QoS) server 100 with enough information to determine a home mobile network operator (MNO) for the requesting client device 108 .
- NPDB number portability database
- MNO local mobile network operator
- the quality of service (QoS) server 100 uses a quality of service (QoS) application profile ID, defined in the application quality of service (QoS) request message, to determine whether or not the requesting over-the-top (OTT) application is authorized to influence quality of service (QoS) treatment on the home mobile network operator (MNO).
- QoS quality of service
- step 20 of FIG. 3 if the over-the-top (OTT) application is permitted to influence quality of service (QoS) settings on the home mobile network operator (MNO), then the quality of service (QoS) server 100 queries a local virtual private network (VPN) tunneling information database 250 to determine actual IP packet information associated with application data routed by the over-the-top (OTT) application over the virtual private network (VPN) tunnel 114 .
- QoS quality of service
- the quality of service (QoS) server 100 sends a diameter authentication/authorization request (AAR) message with appropriate quality of service (QoS) information and appropriate IP tunneling data to a policy and charging rules function (PCRF) 104 on the client devices' 108 home mobile network operator (MNO).
- AAR diameter authentication/authorization request
- QoS quality of service
- IP tunneling data to a policy and charging rules function (PCRF) 104 on the client devices' 108 home mobile network operator (MNO).
- PCRF policy and charging rules function
- Appropriate quality of service (QoS) information depends on the type of virtual private network (VPN) tunnel 114 routing data.
- VPN virtual private network
- the diameter authentication/authorization request (AAR) message assigns quality of service (QoS) rules defined in the application quality of service (QoS) request message to all application data routed over the virtual private network (VPN) tunnel 114 , as previously described in steps 11 - 13 . This assignment allows mapping to the application quality of service (QoS) request message.
- QoS quality of service
- the quality of service (QoS) server 100 assigns quality of service (QoS) rules defined in the application quality of service (QoS) request message to application data being routed for the requesting over-the-top (OTT) application, only.
- the quality of service (QoS) server 100 sends a diameter authentication/authorization request (AAR) message with appropriate quality of service (QoS) rules and appropriate tunnel packet identification information to a policy and charging rules function (PCRF) 104 on the client devices 108 home mobile network operator (MNO).
- AAR authentication/authorization request
- PCRF policy and charging rules function
- Tunnel packet identification information sent to the policy and charging rules function (PCRF) must enable the policy and charging rules function (PCRF) to identify which tunnel packets to assign the requested quality of service (QoS) designation.
- the policy and charging rules function (PCRF) 104 on the client devices' 108 home mobile network operator (MNO) receives quality of service (QoS) information and returns a diameter authentication/authorization answer (AAA) message to the quality of service (QoS) server 100 .
- QoS quality of service
- AAA diameter authentication/authorization answer
- step 23 the quality of service (QoS) server 100 sends a quality of service (QoS) application response message with an appropriate status value to the over-the-top (OTT) application server 110 .
- QoS quality of service
- a quality of service (QoS) application response message preferably comprises: a message ID, an application identifier, and a status identifier.
- a status identifier included in a status field of a quality of service (QoS) application response message may be any one or more of the following: a success status identifier ( 100 ), a quality of service (QoS) system failure status identifier ( 200 ) (indicating a default failure or unexpected failure with no available details), a failed validation of application identifier/access credentials status identifier ( 201 ), a failed validation of quality of service (QoS) profile ID status identifier ( 202 ), a quality of service (QoS) system failure reserved message status identifier (defined per quality of service (QoS) implementation and used to explain a unique system failure) ( 203 - 299 ), a PCRF unavailable status identifier ( 300 ), and/or an AAR/AAA message failure status identifier ( 400 ), wherein the entire contents of the AAA message is embedded in the status field.
- a success status identifier 100
- QoS quality of service
- 200 indicating a default failure or unexpected failure with no
- the over-the-top (OTT) application client 120 can proceed to transmit and consume data for service delivery purposes (i.e. the over-the-top (OTT) client 120 delivers a service as available to its' functionality and thereby consumes IP bandwidth as a result of service fulfillment).
- the over-the-top (OTT) application client 120 on the user equipment 108 either initiates or receives a request to begin service fulfillment.
- the over-the-top (OTT) application server 110 attempts to establish a mutually authenticated (client 120 and server 110 ) transport layer security (TLS)/secure sockets layer (SSL) connection with the quality of service (QoS) server 100 (following standard transport layer security (TLS)/secure sockets layer (SSL) procedures for mutual authentication).
- TLS transport layer security
- SSL secure sockets layer
- the over-the-top (OTT) application server 110 sends an application quality of service (QoS) request message over the virtual private network (VPN) tunnel 114 to the quality of service (QoS) server 100 , to request that a desired level of quality of service (QoS) treatment be applied to application data routed by the over-the-top (OTT) application over the virtual private network (VPN) tunnel 114 .
- QoS application quality of service
- the quality of service (QoS) server 100 then performs application quality of service (QoS) request message validation on the received application quality of service (QoS) request message, identifies a home mobile network operator (MNO) for the requesting client user equipment (UE) 108 , sends appropriate quality of service (QoS) data to a home policy and charging rules function (PCRF) 104 based on the type of virtual private network (VPN) tunnel 114 routing application data, and subsequently forwards a quality of service (QoS) application response message to the over-the-top (OTT) application server 110 , as previously described in steps 17 - 23 .
- QoS application quality of service
- OTT over-the-top
- the over-the-top (OTT) application server 110 informs the quality of service (QoS) server 100 of the service termination, to trigger reserved quality of service (QoS) values to be terminated on the client devices' 108 home mobile network operator (MNO).
- QoS quality of service
- MNO home mobile network operator
- the over-the-top (OTT) application server 110 detects a termination of signaling or service on the over-the-top (OTT) application client user equipment (UE) 108
- the over-the-top (OTT) application server 110 attempts to establish a mutually authenticated (client 120 and server 110 ) TLS/SSL connection with the quality of service (QoS) server 100 (following standard TLS/SSL procedures for mutual authentication).
- client 120 and server 110 the over-the-top (OTT) application server 110 attempts to establish a mutually authenticated (client 120 and server 110 ) TLS/SSL connection with the quality of service (QoS) server 100 (following standard TLS/SSL procedures for mutual authentication).
- QoS quality of service
- the over-the-top (OTT) application server 110 sends an application quality of service (QoS) termination message to the quality of service (QoS) server 100 .
- QoS application quality of service
- an application quality of service (QoS) termination message preferably includes: a message ID (an identifier defined by, and unique to, a requesting over-the-top (OTT) application), an application identifier (as described in 3GPP series 29.214 specification), access credentials (e.g.
- a secret/password public key infrastructure (PKI) verification, etc. a quality of service (QoS) application profile ID, a source framed IP address (an attribute-value part (AVP)) or framed IPv6 prefix (an attribute-value part (AVP), RFC 4005 [12]), a service uniform resource name (URN) (an attribute-value part (AVP), 3GPP 29.214), a reservation priority (TS 183.017 [15]) (a vendor is preferably set to European telecommunications standards institute (ETSI) (13019) [15]), and a subscription ID (RFC 4006 [14]), identifying a particular subscription, e.g., international mobile subscriber identity (IMSI), mobile station integrated services digital network (MSISDN), etc.
- IMSI international mobile subscriber identity
- MSISDN mobile station integrated services digital network
- the quality of service (QoS) server 100 performs application quality of service (QoS) termination message validation, as portrayed in step 36 .
- QoS application quality of service
- the quality of service (QoS) server 100 validates the application identifier and access credentials (e.g., a secret/password public key infrastructure (PKI) verification, etc.) received in the application quality of service (QoS) termination message against application profile data maintained in a local application information database 220 .
- PKI public key infrastructure
- the quality of service (QoS) server 100 sends a diameter session termination request (STR) message to the policy and charging rules function (PCRF) 104 on the over-the-top (OTT) application client device's 108 home mobile network operator (MNO), to indicate that service/signaling has been terminated.
- STR diameter session termination request
- PCRF policy and charging rules function
- the policy and charging rules function (PCRF) 104 responds to the quality of service (QoS) server 100 with a diameter session termination answer (STA) message, and the quality of service (QoS) server 100 subsequently sends an application quality of service (QoS) response message (including an appropriate status value) to the requesting over-the-top (OTT) application server 110 .
- QoS quality of service
- STA diameter session termination answer
- OTT over-the-top
- the virtual private network (VPN) client 118 and/or server 112 sends an IPSec tunnel mapping table, containing appropriate tunnel termination information (tunneling information depicted in Table 1) to the quality of service (QoS) server 100 , once the virtual private network (VPN) tunnel 114 is terminated.
- QoS quality of service
- the virtual private network (VPN) client 118 /server 112 sends a VPN quality of service (QoS) termination message with appropriate tunneling information (tunneling information depicted in Table 1) to the quality of service (QoS) server 100 when the virtual private network (VPN) tunnel 114 is terminated.
- the virtual private network (VPN) client 118 sends a VPN quality of service (QoS) termination message to the quality of service (QoS) server 100 via a conventional Gi/SGi interface 310 .
- a VPN quality of service (QoS) termination message preferably includes access credentials and a tunnel source and destination IP address, to enable the quality of service (QoS) server to identify which tunnel is being terminated and to determine if a pending quality of service (QoS) configuration in the wireless network need be removed as a result of the tunnel termination.
- QoS quality of service
- a quality of service (QoS) termination message is typically preceded by a session termination. However, this may not always be the case.
- the quality of service (QoS) server 100 receives the VPN quality of service (QoS) termination message and appropriately responds to the virtual private network (VPN) client 118 /server 112 with a VPN quality of service (QoS) response message.
- VPN virtual private network
- LTE long term evolution
- E-UMTS evolved-universal mobile telecommunications system
- LTE long term evolution
- Wi-Fi Wi-Fi
- Inventive quality of service (QoS) logic may and should be extended to support other scenarios, such as scenarios described as “Application Function” logic in 3GPP series 29 specifications.
- VPN virtual private network
- SPI security parameter index
- Identification of this nature may reveal an associative characteristic of some virtual private network (VPN) packets.
- Implementers of the inventive technology may wish to determine if additional security, additional encryption, etc., is required to compensate for the reveal of the associative nature of packets.
- the present invention has particular applicability to United States federal agencies, such as the Federal Emergency Management Agency (FEMA), and the Department of Homeland Security (DHS), etc., as well as to emergency first responders, large over-the-top (OTT) application providers (e.g., GoogleTM, AppleTM, etc.), and enhanced long term evolution (LTE) policy and charging rules function(s) (PCRF), from policy and charging rules function (PCRF) vendors.
- FEMA Federal Emergency Management Agency
- DHS Department of Homeland Security
- OTT over-the-top
- PCRF policy and charging rules function
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Conventional quality of service (QoS) treatment is extended to over-the-top (OTT) applications transmitting data over a commercial wireless network via a virtual private network (VPN) tunnel. An over-the-top (OTT) application server and a VPN client/server routing data to/from that OTT application server via a VPN tunnel, are integrated with a quality of service (QoS) server to enable the OTT application server and/or VPN client/server to request and get desired QoS treatment for application data routed by the OTT application server over the VPN tunnel. The QoS server forwards QoS rules received in a QoS request message to a policy and charging rules function (PCRF) on the OTT application/VPN client devices' home mobile network operator (MNO). If the client device is roaming, the PCRF on the home MNO forwards QoS rules to a PCRF on a serving MNO. QoS treatment is then carried out by the PCRF in a conventional manner.
Description
- The present invention is a continuation-in-part of U.S. application Ser. No. 14/032,913, filed Sep. 20, 2013, entitled “Mechanisms For Quality of Service to Over the Top Applications For Use in Commercial Wireless Networks”; which claims priority from U.S. Provisional No. 61/714,944, filed Oct. 17, 2012, entitled “Mechanisms for Quality of Service to Over the Top Applications For Use In Commercial Wireless Networks”. The present application also claims priority from U.S. Provisional No. 61/815,976, filed Apr. 25, 2013, entitled “Quality of Service to Over the Top Applications Used with VPN”; and from U.S. Provisional No. 61/829,745, filed May 31, 2013, entitled “Quality of Service to Over the Top Applications Used with VPN”. The entirety of all four of these applications are expressly incorporated herein by reference.
- 1. Field of the Invention
- This invention relates generally to Quality of Service (QoS) control for Virtual Private Network(s) (VPNs) established between smart phones and private networks (e.g., enterprise or agency intranet) over Long Term Evolution (LTE) commercial wireless networks. These VPN(s) may be used by smart phone applications to access data in the cloud in a secure manner and typically involve tunneling of original application IP packets in an encrypted fashion inside of an outer IP packet.
- 2. Background of Related Art
- Verizon Wireless™ has recently become the first commercial service provider to fully launch a network with Long Term Evolution (LTE) 4G wireless broadband technology. Long Term Evolution (LTE) 4G wireless broadband technology is a recent technology that supports a fast and efficient all-Internet Protocol (IP) network (i.e., a network that provides services, e.g., voice, video, data, messaging, etc., solely over the Internet). It is expected that the majority of commercial service providers will also adopt an all-Internet Protocol (IP) network at some time in the near future.
- As the future of technology gears toward an all-IP network, the number of available over-the-top (OTT) applications is expected to increase. An over-the-top (OTT) application is an application that uses a data channel provided by an Internet service provider (ISP) to connect to the Internet instead of using any special data handling features or network services offered thereby.
- In accordance with conventional technology, over-the-top (OTT) application data is sometimes routed over a commercial wireless network via a virtual private network (VPN) tunnel (which involves the tunneling of original IP packets inside outer IP packets in an encrypted fashion). A virtual private network (VPN) tunnel provides additional transmission security to over-the-top (OTT) application data, which is especially helpful to over-the-top (OTT) applications that lack end-to-end encryption on their network connections.
- Quality of service (QoS) refers to a set of performance characteristics by which a commercial wireless network is expected to convey data traffic to and from a client (quality of service (QoS) control mechanisms are applied to both the wireless and wireline components of a commercial network). Specific performance characteristics may include throughput (i.e. data quantity transmitted per unit time), latency (i.e. time delay between transmission and receipt of data), loss rate (i.e. frequency by which a commercial wireless network fails to deliver portions of transmitted data), jitter (i.e. a measure of variance of other characteristics), etc.
- Currently, there exist several inherent limitations to the quality of service (QoS) treatment that a commercial wireless network is able to provide its' clients. For example, the maximum throughput that a commercial wireless network is able to provide across all clients is dependant on: a spectrum allocation held by the commercial wireless network, a backhaul infrastructure setup between cellular towers and fixed infrastructure within the commercial wireless network, the number of cellular towers in use within the commercial wireless network, the size of a footprint assigned to each cellular tower in use within the commercial wireless network, and any sources of electromagnetic interference within the commercial wireless network.
- It is found that applications (e.g. smart phone applications) typically run better (i.e., perform more objective work per unit time and provide better user experience) when they are receiving a higher level of quality of service (QoS) treatment from a commercial wireless network as opposed to a lower level of quality of service (QoS) treatment. Consequently, many clients/service providers enter into contractual agreements with commercial wireless networks to ensure that they receive a data conveyance that is at-or-above a desired minimum performance level. For example, a commercial wireless network may agree (in exchange for monetary compensation) to provide a minimum of 12 kilobit/second throughput and a minimum of 0.1 second latency to a client user equipment (UE) that desires to receive real-time streaming video feed over that wireless network.
- Commercial wireless networks use well-known internal techniques to ensure that contracted clients receive a pre-negotiated level of quality of service (QoS) treatment. For example, a network operator may delay transmitting data for one low-level quality of service (QoS) client to prioritize data transmission for another high-level quality of service (QoS) client. Likewise, a network operator may discard data packets transmitted to/from one low-level quality of service (QoS) client more frequently, to ensure data conveyance for another high-level quality of service (QoS) client.
- Unfortunately, vendors of over-the-top (OTT) applications and associated data do not typically enter into contractual quality of service (QoS) agreements with commercial wireless networks (e.g. Long Term Evolution (LTE) networks). Therefore, over-the-top (OTT) applications are typically unable to benefit from quality of service (QoS) control mechanisms (e.g, priority, packet delay, guaranteed bit rate, etc.) available thereon. Instead, most over-the-top (OTT) applications (e.g., Skype, Netflix, etc.) provide services on a best-effort basis (i.e., data delivery, efficiency not guaranteed).
- Differentiated Services (DiffServ) has defined a mechanism for classifying and managing network traffic on modern Internet Protocol (IP) networks, for the purposes of providing quality of service (QoS) treatment thereon. In particular, DiffSery uses a 6 bit field (i.e. a DS field) in an IP header for packet classification purposes.
- In accordance with conventional DiffSery technology, a DS field may be influenced (set) by an application generating IP packets. Moreover, a virtual private network (VPN) client may copy a DiffSery header from an incoming application IP packet (that will eventually be encapsulated) to an IP header of a tunneling IP packet to extend DiffSery quality of service (QoS) treatment to a virtual private network (VPN) environment.
- However, though smart phone applications, application cores in the cloud, and virtual private network (VPN) software may all influence the setting of a DS field, there is no guarantee that an Internet Protocol (IP) network (e.g. a long term evolution (LTE) network) will honor a DS field setting and provide desired quality of service (QoS) treatment, being that: first, the honoring of a DS field is not mandated by current standards and, second, triggering quality of service (QoS) treatment in such a fashion defeats the purpose of quality of service (QoS) control as, conceivably, all types of data traffic flowing through an IP network could be marked for preferential treatment by a source application.
- As commercial wireless networks begin carrying data for over-the-top (OTT) mission critical applications, such as applications used by emergency dispatch personnel and emergency first responders, a best-effort treatment of over-the-top (OTT) applications will no longer be acceptable. This is especially true in times of disaster, when networks are likely heavily congested. Hence, a successful means of extending quality of service (QoS) treatment to over-the-top (OTT) applications, including over-the-top (OTT) applications transmitting data over a virtual private network (VPN) tunnel, is needed.
- A method and apparatus for extending conventional quality of service (QoS) treatment to over-the-top (OTT) applications transmitting data over a commercial wireless network via a virtual private network (VPN) tunnel, comprises a quality of service (QoS) server. In accordance with the principles of the present invention, an over-the-top (OTT) application server and a virtual private network (VPN) client/server routing data to/from the over-the-top (OTT) application server over a virtual private network (VPN) tunnel, are each integrated with a quality of service (QoS) server. Following integration, the over-the-top (OTT) application server and/or the virtual private network (VPN) client/server may request and get desired quality of service (QoS) treatment for application data routed by the over-the-top (OTT) application over the virtual private network (VPN) tunnel. The present invention is applicable to both single-tenant virtual private network (VPN) tunnels and multi-tenant virtual private network (VPN) tunnels.
- In accordance with the principles of the present invention, a single-tenant virtual private network (VPN) tunnel (i.e. a virtual private network (VPN) tunnel that is treated as a single application) is only permitted one quality of service (QoS) designation at a time. Hence, a quality of service (QoS) designation requested for/by an application routing data over a single-tenant virtual private network (VPN) tunnel is applied to all application data routed over that virtual private network (VPN) tunnel.
- Alternatively, applications routing data over a multi-tenant virtual private network (VPN) tunnel are acknowledged independently and assigned their own individual quality of service (QoS) designations. Hence, a quality of service (QoS) designation requested for/by an application routing data over a multi-tenant virtual private network (VPN) tunnel is applied to application data routed by that requesting over-the-top (OTT) application, only. In accordance with the principles of the present invention, a multi-tenant virtual private network (VPN) tunnel may define a default quality of service (QoS) designation for application data routed to/from applications that have not indicated a preferred quality of service (QoS) designation.
- In accordance with the principles of the present invention, the quality of service (QoS) server forwards desired quality of service (QoS) rules embedded in a quality of service (QoS) request message to a policy and charging rules function (PCRF) on a requesting over-the-top (OTT) application/virtual private network (VPN) client devices' home mobile network operator (MNO). If a client device is roaming, then the policy and charging rules function (PCRF) on the client devices' home mobile network operator (MNO) forwards received quality of service (QoS) rules to a policy and charging rules function (PCRF) serving the client device. Quality of service (QoS) treatment is then carried out in a conventional manner by the serving policy and charging rules function (PCRF).
- In accordance with the principles of the present invention, a connection between a quality of service (QoS) server and a policy and charging rules function (PCRF) is preferably established via a diameter Rx interface. Accordingly, the primary function of a quality of service (QoS) server is to translate diameter protocol messages to other communication mediums and vice versa.
- In accordance with the principles of the present invention, an over-the-top (OTT) application must provide identification details and register services and application characteristics with the quality of service (QoS) server before that application is permitted to request quality of service (QoS) treatment therefrom. During registration with the quality of service (QoS) server, an over-the-top (OTT) application is required to provision one or more quality of service (QoS) application profiles, each indicating a desired level of quality of service (QoS).
- In accordance with the principles of the present invention, a virtual private network (VPN) client/server must furnish relevant tunneling information to the quality of service (QoS) server before that virtual private network (VPN) client/server is permitted to request quality of service (QoS) treatment therefrom. Relevant tunneling information varies depending upon a type of virtual private network (VPN) tunnel established. In particular, during registration with the quality of service (Qos) server, a single-tenant virtual private network (VPN) tunnel is required to provision identification details and one or more quality of service (QoS) application profiles on the quality of service (QoS) server. Alternatively, during registration with the quality of service (Qos) server, a multi-tenant virtual private network (VPN) tunnel must provision identification details and adequate tunneling information on the quality of service (QoS) server, but need not preprovision any quality of service (QoS) application profiles. Tunneling information furnished to the quality of service (QoS) server for a multi-tenant virtual private network (VPN) tunnel must enable the quality of service (QoS) to identify IP packets associated with application data routed thereover.
- In accordance with the principles of the present invention, a quality of service (QoS) application profile ID identifying a particular quality of service (QoS) application profile (i.e. quality of service (QoS) rules), is included in each quality of service (QoS) request message sent to the quality of service (QoS) server. A quality of service (QoS) application profile ID indicates to the quality of service (QoS) server a particular quality of service (QoS) application profile to invoke.
- When an over-the-top (OTT) application server detects a termination of signaling or service on an over-the-top (OTT) application client device, the over-the-top (OTT) application server sends a quality of service (QoS) termination message to the quality of service (QoS) server, to indicate that reserved quality of service (QoS) values may be terminated on the client devices' home mobile network operator (MNO).
- Likewise, a virtual private network (VPN) client/server must inform the quality of service (QoS) server when a virtual private network (VPN) tunnel has terminated.
- Features and advantages of the present invention will become apparent to those skilled in the art from the following description with reference to the drawings, in which:
-
FIG. 1 depicts an exemplary network structure for extending conventional quality of service (QoS) treatment to over-the-top (OTT) applications routing data over a commercial wireless network via a virtual private network (VPN) tunnel, in accordance with the principles of the present invention. -
FIG. 2 depicts an exemplary quality of service (QoS) server architecture, in accordance with the principles of the present invention. -
FIG. 3 depicts an exemplary process flow for extending quality of service (QoS) treatment to over-the-top (OTT) applications routing data over a commercial wireless network via a virtual private network (VPN) tunnel, in accordance with the principles of the present invention. -
FIG. 4 depicts conventional encryption and encapsulation of an original IP packet, in accordance with conventional IPSec virtual private network (VPN) technology. -
FIG. 5 depicts a conventional single-tenant virtual private network (VPN) tunnel. -
FIG. 6 depicts a conventional multi-tenant virtual private network (VPN) tunnel. - The present invention extends conventional quality of service (QoS) treatment to over-the-top (OTT) applications transmitting data over a commercial wireless network (e.g. a long term evolution (LTE) network) via a virtual private network (VPN) tunnel.
- New wireless standards, such as long term evolution (LTE), only specify data connectivity, and do not specify any applications. Applications, rather, are expected to be facilitated via carrier-hosted application frameworks (e.g. an internet multimedia system (IMS)).
- To ensure that applications carried out via carrier-hosted application frameworks operate at a desired level of quality of service (QoS) (e.g. packet delay, priority, etc.), new wireless standards have defined a policy and charging rules function (PCRF). A policy and charging rules function (PCRF) is a network element (in a long term evolution (LTE) packet core) that may be accessed by carrier-hosted application frameworks (e.g. IMS) (via a diameter protocol based interface (Rx)) for the purposes of providing quality of service (QoS) treatment to applications.
- Unfortunately, applications to which policy and charging rules functions (PCRF) are expected to extend quality of service (QoS) treatment, do not include over-the-top (OTT) applications. An over-the-top (OTT) application is an application that provides services/content to a client user equipment (UE) over the Internet, absent the involvement of an Internet service provider (ISP). Hence, conventional over-the-top (OTT) applications are not facilitated via carrier-hosted application frameworks, and are thus not able to benefit from quality of service (QoS) treatment available on today's commercial wireless networks. Rather, conventional over-the-top (OTT) applications are typically forced to operate on a best-effort basis (i.e. data delivery, efficiency not guaranteed).
- With the future of technology gearing towards an all IP-network (e.g. a long term evolution (LTE) network), over-the-top (OTT) applications are expected to become increasingly common. As commercial wireless networks begin carrying data for over-the-top (OTT) mission critical applications, such as those applications used by emergency dispatch personnel and emergency first responders, a best effort treatment of over-the-top (OTT) application data will no longer be acceptable.
- The present invention expands a method of extending conventional quality of service (QoS) treatment to over-the-top (OTT) applications routing data over a commercial wireless network, as disclosed in co-pending and co-owned U.S. patent application Ser. No. 14/032,913, filed Sep. 20, 2013, entitled: “MECHANISMS FOR QUALITY OF SERVICE TO OVER THE TOP APPLICATIONS FOR USE IN COMMERCIAL WIRELESS NETWORKS”, claiming priority from U.S. Provisional Application No. 61/703,554, filed Sep. 20, 2012, entitled: “MECHANISMS FOR QUALITY OF SERVICE TO OVER THE TOP APPLICATIONS FOR USE IN COMMERCIAL WIRELESS NETWORKS”, and from U.S. Provisional No. 61/714,944, filed Oct. 17, 2012, entitled “MECHANISMS FOR QUALITY OF SERVICE TO OVER THE TOP APPLICATIONS FOR USE IN COMMERCIAL WIRELESS NETWORKS”, all of which are explicitly incorporated herein by reference. Mechanisms for quality of service control disclosed in U.S. Ser. No. 14/032,913 address a scenario wherein an over-the-top (OTT) application connects to a cloud based application infrastructure directly.
- The present invention addresses a variation of the scenario described in U.S. application Ser. No. 14/032,913. In particular, the present invention addresses a scenario wherein an over-the-top (OTT) application client on a user equipment (UE) is connected to a cloud based over-the-top (OTT) application server via a virtual private network (VPN) connection. A conventional virtual private network (VPN) connection provides additional transport security to over-the-top (OTT) application data traversing a commercial wireless network, by tunneling original IP packets inside outer IP packets in an encrypted fashion. Mechanisms for establishing a virtual private network (VPN) tunnel appropriate to convey over-the-top (OTT) application data are well known to those skilled in the art.
- In accordance with the principles of the present invention, conventional quality of service (QoS) treatment is extended to over-the-top (OTT) applications transmitting data over a commercial wireless network (e.g. a long term evolution (LTE) network) via a virtual private network (VPN) tunnel, without requiring that modifications be made to over-the-top (OTT) applications, and without requiring that over-the-top (OTT) application developers negotiate separate quality of service (QoS) agreements with mobile network operators (MNO). Moreover, the present invention extends conventional quality of service (QoS) treatment to virtual private networks (VPN) carrying over-the-top (OTT) application data without burdening virtual private networks (VPN) with network integration aspects, such as: knowledge of user location, knowledge of a policy and charging rules function (PCRF), knowledge of a long term evolution (LTE) packet core, etc.
- In accordance with the principles of the present invention, an over-the-top (OTT) application server and a virtual private network (VPN) client/server carrying data to/from that over-the-top (OTT) application server over a virtual private network (VPN) tunnel, are each integrated with an inventive quality of service (QoS) server. Following integration, the over-the-top (OTT) application server and/or the virtual private network (VPN) client/server may send a quality of service (QoS) request message to the inventive quality of service (QoS) server (via an appropriate virtual private network (VPN) client/server interface or over-the-top (OTT) application interface) to request that desired quality of service (QoS) treatment (identified by a quality of service (QoS) application profile ID) be applied to application data routed by the over-the-top (OTT) application over the virtual private network (VPN) tunnel.
- The inventive quality of service (QoS) server forwards quality of service (QoS) rules embedded in a quality of service (QoS) request message to a policy and charging rules function (PCRF) residing on a requesting over-the-top (OTT) application/virtual private network (VPN) client devices' home mobile network operator (MNO). If the client device is roaming, then the policy and charging rules function (PCRF) on that device's home mobile network operator (MNO) forwards quality of service (QoS) rules to a policy and charging rules function (PCRF) serving the client device. Quality of service (QoS) treatment is then carried out by the policy and charging rules function (PCRF) in a conventional manner.
- In accordance with the principles of the present invention, an over-the-top (OTT) application server and/or a virtual private network (VPN) client/server may modify a previously requested level of quality of service (QoS) treatment, when a previously requested level of quality of service (QoS) treatment is not resulting in desired performance.
- The inventive solution may be applied to various virtual private network (VPN) technologies, including: a
layer 2 tunneling protocol (L2TP) technology, a point-to-point tunneling protocol (PPTP) technology, a transport layer security/virtual private network (VPN) technology, etc. However, for illustrative purposes, the present invention is described herein via use of an IPSec virtual private network (VPN) technology configured in tunnel mode. In accordance with conventional IPSec virtual private network (VPN) technology, all IP datagrams (including both datagram header and datagram packet) routed over a virtual private network (VPN) tunnel are first encapsulated inside new IP datagrams with IPSec headers. -
FIG. 4 depicts conventional encryption and encapsulation of an original IP packet, in accordance with conventional IPSec virtual private network (VPN) technology. - In particular, an original IP packet 420 (including an
original IP header 440 and an original application payload 450) is encrypted 400 a, 400 b and encapsulated in anouter IP packet 410 with anIPSec header 430 before it is routed over a conventional IPSec virtual private network (VPN) tunnel. A virtual private network (VPN) client/server also interprets anoriginal IP packet 420 and assigns an appropriate security parameter index (SPI) value (in accordance with a preconfigured security parameter index (SPI) value) thereto before routing the IP packet over a virtual private network (VPN) tunnel. A security parameter index (SPI) value serves as an index to a conventional security association database (SADB) (i.e. a database that maintains information for a virtual private network (VPN) tunnel) maintained for a virtual private network (VPN) tunnel. A security association database (SADB) preferably includes some or all of the following information: security association information (i.e. security parameter index, IPSec protocol, IP destination address) and security policy information (i.e. IP source address, IP destination address, fully qualified domain name, source port number, destination port number, quality of service (QoS) application profile ID). - The present invention is applicable to both single-tenant virtual private network (VPN) tunnels and multi-tenant virtual private network (VPN) tunnels.
-
FIG. 5 depicts a conventional single-tenant virtual private network (VPN) tunnel. - In particular, a single-tenant virtual private network (VPN)
tunnel 500 is always treated as a single application, regardless of howmany applications 510 actually utilize thetunnel 500. Therefore, a single-tenant virtual private network (VPN)tunnel 500 is only permitted one quality of service (QoS)designation 540 at a time. In accordance with the principles of the present invention, a quality of service (QoS) designation requested for/by an application routing data over a single-tenant virtual private network (VPN)tunnel 500 is applied to allapplication data 510 routed over that virtual private network (VPN)tunnel 500. -
FIG. 6 depicts a conventional multi-tenant virtual private network (VPN) tunnel. - As portrayed in
FIG. 6 ,applications 530 transmitting data over a multi-tenant virtual private network (VPN)tunnel 520 are acknowledged independently and may thus be assigned their own individual quality of service (QoS)designations 550. A quality of service (QoS)designation 550 requested for/by an application routing data over a multi-tenant virtual private network (VPN)tunnel 500 is only applied to application data routed by that application. -
FIG. 1 depicts an exemplary network structure for extending conventional quality of service (QoS) treatment to over-the-top (OTT) applications routing data over a commercial wireless network via a virtual private network (VPN) tunnel, in accordance with the principles of the present invention. - In particular, as depicted in
FIG. 1 , a quality of service (QoS)server 100 is configured to directly interface with one or morecommercial wireless networks 102 a, 102 b via a conventional policy and charging rules function (PCRF) (i.e. an IP multimedia subsystem (IMS)/long term evolution (LTE) network component) 104. In accordance with the principles of the present invention, a connection between a quality of service (QoS)server 100 and a policy and charging rules function (PCRF) 104 is preferably established via a diameter Rx interface 106 (3GPP specifications 29.209, 29.214). Hence, the primary function of a quality of service (QoS)server 100 is to translatediameter protocol interface 106 messages to other communication mediums and vice versa. - Once a connection is established between a policy and charging rules function (PCRF) 104 and the quality of service (QoS)
server 100, the inventive quality of service (QoS)server 100 takes on the role of a special application function (AF) connected on the backend (i.e. not accessible to a user) 110 of one or more disparate applications. The quality of service (QoS)server 100 also establishes a connection with a virtual private network (VPN)server 112 and/or virtual private network (VPN)client 118, when application data exchanged between an over-the-top (OTT)application client 120 and an over-the-top (OTT)application server 110 happens over a virtual private network (VPN) tunnel 114. - As depicted in
FIG. 1 , the inventive quality of service (QoS)server 100 uses a secure virtual private network (VPN) client/server interface 116 to interface with a virtual private network (VPN)client 118/server 112 on either end of a virtual private network (VPN) tunnel 114. In accordance with the principles of the present invention, virtual private network (VPN)clients 118/servers 112 use the virtual private network (VPN) client/server interface 116 to provide relevant tunneling information to the quality of service (QoS)server 100. Relevant tunneling information enables the quality of service (QoS)server 100 to identify IP packets associated with over-the-top (OTT) application data transmitted over a virtual private network (VPN) tunnel 114. - In accordance with the principles of the present invention, a virtual private network (VPN) tunnel 114 is established between a virtual private network (VPN)
client 118 on auser equipment 108, and a fixed infrastructure virtual private network (VPN)server 112, so that data traffic transmitted to/from one or more over-the-top (OTT)application clients 120 on the user equipment (UE) 108 may traverse the virtual private network (VPN) tunnel 114. A virtual private network (VPN) tunnel 114 encrypts and encapsulates an original IP packet inside an outer IP packet while the IP packet is traversing a commercial wireless network. An underlyingcommercial wireless network 102 a, 102 b is typically configured to provide a certain level of quality of service (QoS) treatment to traffic traversing a virtual private network (VPN) tunnel 114. - In accordance with the principles of the present invention, the quality of service (QoS)
server 100 must be able to communicate withbackend applications 110, carrier policy and charging rules (PCRF) function(s) 104, and virtual private network (VPN)clients 118/servers 112, simultaneously. Simultaneous communication may be permitted via a firewall setting and/or other network configuration rules. - In accordance with the principles of the present invention, a quality of service (QoS)
server 100 may be located separate from a mobile network operator (MNO) 102 a, 102 b or co-located with a mobile network operator (MNO) 102 a, 102 b. Possible mobile network operator (MNO) integration targets currently include: a universal mobile telecommunications system (UMTS), long term evolution (LTE) technology, an evolved-universal mobile telecommunications system (E-UMTS), long term evolution (LTE) technology advanced, and Wi-Fi. The quality of service (QoS)server 100 may easily be extended to support additional network interfaces as technology evolves. -
FIG. 2 depicts an exemplary quality of service (QoS) server architecture, in accordance with the principles of the present invention. - In particular, as portrayed in
FIG. 2 , the inventive quality of service (QoS)server 100 interacts with a mobile network operator (MNO) policy and charging rules function (PCRF) interface (a diameter protocol interface) 106, an over-the-top (OTT)application interface 210, a number portability database (NPDB)interface 240, and a virtual private network (VPN) client/server interface 116 to extend quality of service (QoS) treatment to applications routing data over acommercial wireless network 102 a, 102 b via a virtual private network (VPN) tunnel 114. - In accordance with the principles of the present invention, the quality of service (QoS)
server 100 maintains profiles and information for over-the-top (OTT) applications in a localapplication information database 220, tunneling and IP packet information for registered virtual private network (VPN) tunnels in a local virtual private network (VPN)tunneling information database 250, and home mobile network operator (MNO) information for over-the-top (OTT) application client devices in a local mobile network operator (MNO)information database 230. - If by chance the quality of service (QoS)
server 100 is not able to find home mobile network operator (MNO) information for a requestingclient device 108 in the local mobile network operator (MNO)information database 230, then the quality of service (QoS)server 100 accesses a number portability database (NPDB)interface 240 to retrieve relevant home mobile network operator (MNO) information from an external number portability database (NPDB) 270. - The over-the-top (OTT)
application interface 210, as depicted inFIG. 2 , is designed to operate over a secure, transport layer security (TLS)/secure sockets layer (SSL) communications channel that utilizes representational state transfer (REST) hypertext transfer protocol (HTTP), hypertext transfer protocol (HTTP), simple object access protocol (SOAP), extensible markup language (XML), etc., message formats. New mediums for the over-the-top (OTT)application interface 210 may be defined and used, as appropriate, as long as application quality of service (QoS) message formats (i.e. attributes and corresponding values included in application quality of service messages) conform minimally to application quality of service (QoS) message formats described herein (i.e. an application quality of service (QoS) request message format, an application quality of service (QoS) response message format, and an application quality of service (QoS) termination message format). As previously stated, the quality of service (QoS)server 100 uses a diameter Rx protocol (3GPP 29.214) to interface 106 with a mobile network operator (MNO) policy and charging rules function (PCRF) 104. A mobile network operator (MNO) policy and charging rules function (PCRF)interface 106, as depicted inFIG. 2 , provides discovery and addressing of a home policy and charging rules function (HPCRF) 104 assigned to a requesting over-the-top (OTT) application/virtual private network (VPN)client device 108. The mobile network operator (MNO) policy and charging rules function (PCRF)interface 106 is also enhanced to allow tracking registration of the following IP header information: a virtual private network (VPN) security parameter index (SPI) (per RFC 2401, as required with IPSec protocol by a virtual private network (VPN) client/server) and an IPSec protocol (per RFC 2401). - In accordance with the principles of the present invention, the quality of service (QoS)
server 100 assumes the role of an application function (AF) and complies with policy and charging rules function (PCRF) 104 discovery and addressing, as described in a 3GPP series 29.213 specification. In support of this 3GPP series 29.213 specification, the quality of service (QoS)server 100 preferably maintains a table with a fully qualified domain name (FQDN) or internet protocol (IP) address of a policy and charging rules function (PCRF) 104, for each supported single policy and charging rules function (PCRF) mobile network operator (MNO), and a diameter routing agent, for each supported multi-policy and charging rules function (PCRF) mobile network operator (MNO). - The quality of service (QoS)
server 100 interfaces with a home policy and charging rules function (HPCRF) 104, regardless as to whether or not a client user equipment (UE) 108 is roaming. A home policy and charging rules function (HPCRF) 104 coordinates a download of quality of service (QoS) rules to a visiting policy and charging rules function (VPCRF) in a roaming network (per 3GPP standards) when a requesting client user equipment (UE) 108 is roaming. - In accordance with the principles of the present invention, number portability databases (NPDB) 270 and the local mobile network operator (MNO) information database 230 (as shown in
FIG. 2 ) support multiple transaction capabilities application part (TCAP) based protocols (e.g., advanced intelligent network (AIN), intelligent network application protocol (INAP), American national standards institute ((ANSI)-41), etc.) for number portability queries, since such protocols support queries from both wireline and wireless networks based on various standards. The quality of service (QoS)server 100 preferably uses a number portability request (NPREQ) TCAP query (per telecommunications industry association/electronic industries association (TIA/EIA)-756A and telecommunications industry association/electronic industries association (TIA/EIA) ANSI41-D specifications) to determine a current mobile network operator (MNO) associated with an over-the-top (OTT)application client device 108. The quality of service (QoS)server 100 may easily be extended to support other protocols for number portability lookup. - As previously stated, the quality of service (QoS)
server 100 uses a virtual private network (VPN) client/server interface 116 to interface with a virtual private network (VPN)client 118 and/or a virtual private network (VPN)server 112. The virtual private network (VPN) client/server interface 116, as portrayed inFIG. 2 , is designed to operate over a secure transport layer security (TLS)/secure sockets layer (SSL) communications channel that utilizes representational state transfer (REST) hypertext transfer protocol (HTTP), hypertext transfer protocol (HTTP), simple object access protocol (SOAP), extensible markup language (XML), etc., message formats. The quality of service (QoS)server 100 may also/alternatively interface with a virtual private network (VPN)client 118 via awireless network connection 260. - New mediums for the virtual private network (VPN) client/
server interface 116 may be defined and used as appropriate, as long as VPN quality of service (QoS) message formats (i.e. attributes and corresponding values included in VPN quality of service (QoS) messages) conform minimally to VPN quality of service (QoS) message formats described herein (i.e. a VPN quality of service (QoS) request message format, a VPN quality of service (QoS) response message format, and a VPN quality of service (QoS) termination message format). Depending upon the implementation, a VPN quality of service (QoS) message may additionally be embedded in a defined message format, e.g., a radius or diameter message format. -
FIG. 3 depicts an exemplary process flow for extending quality of service (QoS) treatment to over-the-top (OTT) applications routing data over a commercial wireless network via a virtual private network (VPN) tunnel, in accordance with the principles of the present invention. - In particular, as shown in step 1 a of
FIG. 3 , a virtual private network (VPN) tunnel performs VPN profile configuration with a quality of service (QoS)server 100 via an authenticated virtual private network (VPN) client/server interface 116. During virtual private network (VPN) profile configuration, a virtual private network (VPN) client/server furnishes relevant tunneling information to the quality of service (QoS)server 100 for a virtual private network (VPN) tunnel established therebetween. Relevant tunneling information varies depending upon the type of virtual private network (VPN) tunnel established. - In particular, a single-tenant virtual private network (VPN)
tunnel 500 provisions one or more quality of service (QoS) application profiles (and corresponding quality of service application profile IDs) on the quality of service (QoS)server 100 during VPN profile configuration. A quality of service (QoS) application profile includes tunnel identification details and indicates a desired level of quality of service (QoS) treatment. - Alternatively, a multi-tenant virtual private network (VPN)
tunnel 520 provisions identification details on the quality of service (QoS)server 100 during VPN profile configuration, but need not provision any quality of service application profiles. Rather, over-the-top (OTT)applications 530 utilizing a multi-tenant virtual private network (VPN)tunnel 520 provision their own quality of service (QoS) application profiles on the quality of service (QoS)server 100 during application profile configuration, performed instep 1 b. A quality of service (QoS) designation requested by an over-the-top (OTT) application transmitting data over a multi-tenant virtual private network (VPN)tunnel 520 is associated to that multi-tenant virtual private network (VPN)tunnel 520. - In accordance with the principles of the present invention, a multi-tenant virtual private network (VPN) 520 tunnel must provide adequate tunneling information (including IPSec security policy and IPSec security association information) to the quality of service (QoS)
server 100 during VPN profile configuration. Adequate tunneling information is any information that enables the quality of service (QoS)server 100 to determine actualIP header information 440 associated with application data routed over the multi-tenant virtual private network (VPN)tunnel 520. Moreover, tunneling information must enable the quality of service (QoS)server 100 to adequately communicate quality of service (QoS) rules defined in a quality of service (QoS) request message to a relevant policy and charging rules function (PCRF) 104. - Table 1 depicts exemplary tunneling information provided to the quality of service (QoS) server during virtual private network (VPN) profile configuration.
-
TABLE 1 Security Association (Tunnel Header Information) Security Policy Information (For Encapsulated Traffic) Security IPSec IP IP IP Fully Source Destination QoS- Parameter Protocol Destination Source Destination Qualified Port Port Application- Index Address Address Address Domain Number Number Profile-ID Name - In particular, as portrayed in Table 1, IPSec security policy information (for encapsulated data traffic) and IPSec security association information (tunnel header information) relevant to a virtual private network (VPN) tunnel is provided to the quality of service (QoS)
server 100 during VPN profile configuration (step 1 a). Relevant IPSec security policy information preferably includes: an IP source address, an IP destination address, a fully qualified domain name, a source port number, a destination port number, and a quality of service application profile ID. Relevant IPSec security association information preferably includes: a security parameter index, an IPSec protocol, and an IP destination address. - Updated tunneling information must be furnished to the quality of service (QoS)
server 100 for each new virtual private network (VPN) tunnel that is established. In accordance with the principles of the present invention, tunneling information may either be preprovisioned on the quality of service (QoS)server 100 during VPN profile configuration, or provided to the quality of service (QoS)server 100 dynamically, via use of a VPN quality of service (QoS) registration message. - As portrayed in
step 1 b ofFIG. 3 , an application performs application profile configuration on the quality of service (QoS)server 100 via an authenticated over-the-top (OTT)application interface 210. In accordance with the principles of the present invention, an over-the-top (OTT) application must provide identification details and register services and application characteristics with a quality of service (QoS)server 100 before that application is permitted to request quality of service (QoS) treatment therefrom. For security purposes, the quality of service (QoS)server 100 only accepts registration attempts from over-the-top (OTT) applications for which the quality of service (QoS)server 100 has been pre-configured to accept registration attempts. Therefore, not all over-the-top (OTT) applications are permitted to register with a quality of service (QoS)server 100. Moreover, over-the-top (OTT) applications that are granted registration with a quality of service (QoS)server 100 are only permitted to receive levels of quality of service (QoS) treatment for which they have been pre-authorized to receive. Quality of service (QoS) requests are validated by the quality of service (QoS)server 100 before they are processed. An over-the-top (OTT) application also identifies service abilities and provisions one or more quality of service (QoS) application profiles on the quality of service (QoS)server 100 during application profile configuration. - However, before an over-the-top (OTT) application can register and provision quality of service (QoS) application profiles on the quality of service (QoS)
server 100, the quality of service (QoS)server 100 must first collect the following data from the over-the-top (OTT) application (more characteristics may be required as new application characteristics present themselves): an over-the-top (OTT) application identifier, over-the-top (OTT) access credentials, one or more quality of service (QoS) application profile IDs, over-the-top (OTT) application characteristics, and one or more mobile network operator (MNO) associations. - In accordance with the principles of the present invention, an over-the-top (OTT) application identifier is a unique string (synchronized with a carrier provided “AF-Application-Identifier”) that is provided to an over-the-top (OTT) application via an out-of-band mechanism. An over-the-top (OTT) application identifier may be prefixed with quality of service (QoS) unique identifiers for use on the quality of service (QoS)
server 100. - Over-the-top (OTT) access credentials (e.g. a secret/password or public key infrastructure (PKI) verification) are a set of credentials agreed upon by an over-the-top (OTT) application and the quality of service (QoS)
server 100 in an out of band manner. - A quality of service (QoS) application profile ID is a quality of service (QoS) specific value, defined per application identifier. More particularly, the quality of service (QoS) application profile ID is defined by the quality of service (QoS)
server 100 and provided to an over-the-top (OTT) application via an out of band mechanism. - In accordance with the principles of the present invention, a quality of service (QoS) application profile ID points to a quality of service (QoS) application profile that is to be provisioned for an over-the-top (OTT) application. A quality of service (QoS) application profile contains application details (e.g. service characteristics, etc.) and indicates a desired level of quality of service (QoS) treatment. A quality of service (QoS) application profile ID is referenced in each quality of service (QoS) request message sent to the quality of service (QoS)
server 100, to indicate to the quality of service (QoS) server 100 a particular quality of service (QoS) application profile to invoke. In accordance with the principles of the present invention, an over-the-top (OTT) application may provision multiple quality of service (QoS) application profiles to indicate varying levels of desired quality of service (QoS). - Over-the-top (OTT) application characteristics provided to the quality of service (QoS)
server 100 during application profile configuration include (this list may be extended as new requirements develop, either by 3GPP specifications or via over-the-top (OTT) evolution): a media component number (i.e. an ordinal number of a media component), a media sub-component (i.e. a set of flows for one flow identifier), an application identifier, a media type (e.g. audio (0), video (1), data (2), application (3), control (4), text (5), message (6), other (0xFFFFFFFF)), a maximum requested bandwidth (Bw) uplink (UL), a maximum requested bandwidth (Bw) downlink (DL), a flow status, a reservation priority, RS bandwidth (Bw), RR bandwidth (Bw), codec data, and a tunnel encapsulation indicator, e.g., yes, no, IPSec, etc. - In accordance with the principles of the present invention, a media sub-component field may include the following characteristics: a flow number (i.e. an ordinal number of the IP flow), a flow description (e.g. uplink (UL) and/or downlink (DL)), a flow status, flow usage, a maximum requested bandwidth (Bw) uplink (UL), a maximum requested bandwidth (Bw) downlink (DL), and an application function (AF) signaling protocol.
- Moreover, a mobile network operator (MNO) associations field provided to the quality of service (QoS)
server 100 during application profile configuration identifies all of the networks for which an over-the-top (OTT) application is authorized to designate quality of service (QoS) settings. Values in a mobile network operator (MNO) associations field are defined per quality of service (QoS) implementation and represent system logical identifiers for the purposes of routing communications to particular policy and charging rules (PCRF) functions. - In accordance with the principles of the present invention, once required application data is furnished to the quality of service (QoS)
server 100, an over-the-top (OTT) application provisions one or more quality of service (QoS) application profiles on the quality of service (QoS)server 100. Following quality of service (QoS) application profile provisioning, the over-the-top (OTT) application may begin submitting registrations to the quality of service (QoS)server 100, on a per user equipment (UE) basis. In accordance with the principles of the present invention, an over-the-top (OTT) application is required to register with the quality of service (QoS)server 100 periodically. - Following application profile configuration, an over-the-top (OTT) application may send quality of service (QoS) requests to the quality of service (QoS)
server 100, on a per user equipment (UE) basis. - As shown in steps 2 a and 2 b of
FIG. 3 , a virtual private network (VPN) tunnel 114 is established between a virtual private network (VPN)client 118 on a user equipment (UE) 108 and a fixed infrastructure virtual private network (VPN)server 112, so as to allow data traffic transmitted to/from one or more over-the-top (OTT) application clients 120 (that have undergone application profile configuration on the quality of service (QoS) server 100) on the user equipment (UE) 108 to traverse the tunnel 114. - In accordance with the principles of the present invention, the virtual private network (VPN)
client 118/server 112 sends a VPN quality of service (QoS) registration message with appropriate tunneling information to the quality of service (QoS)server 100 during VPN tunnel establishment, as depicted insteps 3 a and 3 b ofFIG. 3 . Upon receipt of the VPN quality of service (QoS) registration message, the quality of service (QoS)server 112 returns a VPN quality of service (QoS) registration response message to the virtual private network (VPN)client 118/server 112, as depicted in steps 4 a and 4 b ofFIG. 3 . VPN tunneling information may alternatively be provisioned on the quality of service (QoS)server 100 during VPN profile configuration. - Once VPN registration with the quality of service (QoS)
server 100 is complete, the virtual private network (VPN)client 118/server 112 may send a VPN quality of service (QoS) request message to the quality of service (QoS)server 100 to request desired quality of service (QoS) treatment therefrom, as shown insteps 5 a and 5 b ofFIG. 3 . - In accordance with the principles of the present invention, VPN quality of service (QoS) registration and request messages preferably include: a message ID (i.e. an identifier defined by, and unique to, a requesting virtual private network (VPN)
server 112/client 118), a quality of service (QoS) application profile ID (optional), a publically available mobile network assigned source framed internet protocol (IP) address (an attribute-value pair (AVP)) or framed IPv6 prefix (an attribute-value pair (AVP), RFC 4005 [12]), a flow description (an attribute-value pair (AVP), 3GPP 29.214), a virtual private network (VPN) security parameter index (SPI) (per RFC 2041, as required with IPSec protocol by the virtual private network (VPN) client/server), an IPSec protocol (per RFC 2041), a virtual private network (VPN) IP destination (i.e. a routable IP address for the virtual private network (VPN) server), and a VPN-CS. - A quality of service (QoS) application profile ID in a VPN quality of service (QoS) request message indicates a desired level of quality of service (QoS) treatment. A quality of service (QoS) application profile ID is required in a VPN quality of service (QoS) request message when the message is provided to the quality of service (QoS)
server 100 dynamically. Otherwise, the quality of service (QoS)server 100 derives a quality of service (QoS) application profile ID based on a combination of values embedded in the VPN quality of service (QoS) request message. - A flow description is required in a VPN quality of service (QoS) request message when a quality of service (QoS) application profile ID is not provided therein. In accordance with the principles of the present invention, a flow description must comprise one of the following two directions: ‘in’ or ‘out’, whereas direction ‘in’ refers to an uplink (UL) IP flow and direction ‘out’ refers to a downlink (DL) IP flow. A flow description may also contain: a source and destination IP address (possibly masked), a protocol and a source and destination port (a source port may be omitted to indicate that any source port is allowed). Lists and ranges may not be used to indicate source and/or destination ports. In accordance with the principles of the present invention, the quality of service (QoS)
server 100 accepts VPN quality of service (QoS) request messages from both a virtual private network (VPN)client 118 and a virtual private network (VPN)server 112. Hence, depending upon the implementation, some information may be missing from a VPN quality of service (QoS) request message. - When both a virtual private network (VPN)
server 112 and a virtual private network (VPN)client 118 send a VPN quality of service (QoS) request message to the quality of service (QoS)server 100 for a single VPN connection 114, messages from each source must include a reference to the other, to enable the quality of service (QoS)server 100 to successfully assemble all relevant information and assign an appropriate quality of service (QoS) designation to over-the-top (OTT) application data traversing the virtual private network (VPN) connection 114. A VPN-CS field is preferably used to provide such a reference. - In particular, when VPN quality of service (QoS) request messages are sent by both a virtual private network (VPN)
server 112 and a virtual private network (VPN)client 118 for a single virtual private network (VPN) connection 114, optional attribute tag, ‘VPN-CS’ is preferably included therein. Optional attribute tag ‘VPN-CS’ contains a unique message identifier that is used by both a virtual private network (VPN)server 112 and a virtual private network (VPN)client 118, to show that messages refer to a single virtual private network (VPN) connection 114. - As shown in step 6 of
FIG. 3 , the quality of service (QoS)server 100 performs VPN quality of service (QoS) request message validation in response to a VPN quality of service (QoS) request message received thereon. In particular, during VPN quality of service (QoS) request message validation, the quality of service (QoS)server 100 validates a quality of service (QoS) application profile ID received in the VPN quality of service (QoS) request message. - In accordance with the principles of the present invention, the quality of service (QoS)
server 100 may either determine a quality of service (QoS) application profile ID directly or indirectly from the VPN quality of service (QoS) request message. Indirect determination of a quality of service (QoS) application profile ID includes analyzing and matching VPN quality of service (QoS) request message parameters to an appropriate quality of service (QoS) application profile ID. Once a quality of service (QoS) application profile ID is determined, the quality of service (QoS)server 100 performs one of the following two potential courses of action, depending upon the type of virtual private network (VPN) tunnel 114 established insteps 2 a-4 b. - In particular, if the virtual private network tunnel (VPN) 114 is a multi-tenant virtual private network (VPN)
tunnel 520, then the quality of service (QoS)server 100 records and tracks virtual private network (VPN) 114 tunneling information received in the VPN quality of service (QoS) request message in a virtual private network (VPN)tunneling information database 250, and subsequently returns a VPN quality of service (QoS) response message to the requesting virtual private network (VPN)client 118/server 112, as depicted instep 7. In accordance with the principles of the present invention, the quality of service (QoS)server 100 then waits to receive an application quality of service (QoS) registration message or an application quality of service (QoS) termination message from an over-the-top (OTT) application routing or attempting to route data over the virtual private network (VPN) tunnel 114. - In a multi-tenant virtual private network (VPN) scenario, if a quality of service (QoS) application profile ID received in an application quality of service (QoS) request message differs from a quality of service (QoS) application profile ID embedded in a VPN quality of service (QOS) request message, the quality of service (QoS) application profile ID in the application quality of service (QoS) request message is used to influence quality of service (QoS) treatment.
- Alternatively, if the virtual private network tunnel (VPN) 114 established in
steps 2 a-4 b is a single-tenant virtual private network (VPN)tunnel 500, then the quality of service (QoS)server 100 immediately applies quality of service (QoS) rules received in the VPN quality of service (QoS) registration or request message to all application data routed over the virtual private network (VPN) tunnel 114. The quality of service rules are extracted from the VPN quality of service (QoS) registration message if that is the only message received and VPN quality of services (QoS) request message if both are received. - In particular, when a VPN quality of service (QoS) registration (or request if received) message is received from a single-tenant virtual private network (VPN)
client 118/server 112, the quality of service (QoS)server 100 queries a local mobile network operator (MNO)information database 230 to retrieve home mobile network operator (MNO) information for the over-the-top (OTT) application/virtual private network (VPN)client device 108, as depicted instep 8. If the quality of service (QoS)server 100 cannot find home mobile network operator (MNO) information for the client device in the local mobile network operator (MNO)information database 230, then the quality of service (QoS)server 100 alternatively queries an external number portability database (NPDB) 270 via a number portability database (NPDB)interface 240. Results from either the number portability database (NPDB) 270 or the local mobile network operator (MNO)information database 230 provide the quality of service (QoS)server 100 with enough information to determine a home mobile network operator (MNO) for the over-the-top (OTT) application/VPN client device 108 (step 9). - Once a home mobile network operator (MNO) is identified, the quality of service (QoS)
server 100 uses the quality of service (QoS) application profile ID defined in the VPN quality of service (QoS) registration (or request if received) message to determine whether or not over-the-top (OTT) applications routing data over the virtual private network (VPN) tunnel are authorized to influence quality of service (QoS) treatment on the home mobile network operator (MNO) (step 10). In this particular example, there is only one over-the-top (OTT) application configured to transmit data over the virtual private network (VPN) tunnel 114. - In accordance with the principles of the present invention, if the over-the-top (OTT) application configured to route data over the virtual private network (VPN) tunnel 114 is permitted to influence quality of service (QoS) settings on the home mobile network operator (MNO), then the quality of service (QoS)
server 100 sends a diameter authentication/authorization request (AAR) message with appropriate quality of service (QoS) information to a policy and charging rules function (PCRF) 104 on the client devices' 108 home mobile network operator (MNO), as shown instep 11. - In
step 12, the policy and charging rules function (PCRF) 104 on the client devices' 108 home mobile network operator (MNO) receives the quality of service (QoS) information and returns a diameter authentication/authorization answer (AAA) message to the quality of service (QoS)server 100. - Upon receipt of the diameter authentication/authorization answer (AAA) message, the quality of service (QoS)
server 100 sends a VPN quality of service (QoS) response message to the requestingVPN client 118/server 112, as depicted instep 13. - In accordance with the principles of the present invention, a VPN quality of service (QoS) response message preferably includes: a message ID, an application identifier, and a status identifier. A status identifier included in a status field of a VPN quality of service (QoS) response message may be any one or more of the following: a success status identifier (100), a quality of service (QoS) system failure status identifier (200) (indicating a default failure or unexpected failure with no available details), a failed validation of application identifier/access credentials status identifier (201), a failed validation of quality of service (QoS) profile ID status identifier (202), a quality of service (QoS) system failure reserved message status identifier (defined per quality of service (QoS) implementation and used to explain a unique system failure) (203-299), a PCRF unavailable status identifier (300), and/or an AAR/AAA message failure status identifier (400), wherein the entire contents of the AAA message is embedded in the status field.
- Once the virtual private network (VPN) tunnel 114 is setup between the virtual private network (VPN)
client 118 on theuser equipment 108 and the virtual private network (VPN)server 112, the over-the-top (OTT)application client 120 configured to route data over the virtual private network (VPN) tunnel 114 may use the virtual private network (VPN) tunnel 114 to register with a corresponding over-the-top (OTT) application server 110 (via a Gi/SGi interface 310), as shown insteps 14 a and 14 b ofFIG. 3 . - When the over-the-top (OTT)
application server 110 receives a service registration request from the over-the-top (OTT)application client 120, the over-the-top (OTT)application server 110 may attempt to establish a mutually authenticated (client 120 and server 110) transport layer security (TLS)/secure sockets layer (SSL) connection with the inventive quality of service (QoS) server 100 (via standard TLS/SSL procedures for mutual authentication), as shown instep 15. - If the initial mutual authentication step is successful, then the over-the-top (OTT)
application server 110 sends an application quality of service (QoS) request message to the quality of service (QoS)server 100 to request that a desired level of quality of service (QoS) treatment be applied to application data routed by that over-the-top (OTT) application over the virtual private network (VPN) tunnel 114, as portrayed instep 16. - In accordance with the principles of the present invention, a quality of service (QoS) request message preferably includes: a message ID (i.e. an identifier defined by, and unique to, a requesting over-the-top (OTT) application), an application identifier (as described in 3GPP series 29.214 specification), access credentials (e.g. a secret/password public key infrastructure (PKI) verification, etc.), a quality of service (QoS) application profile ID, a source framed internet protocol (IP) address (an attribute-value pair (AVP)) or framed IPv6 prefix (an attribute-value pair (AVP), RFC 4005 [12]), a service uniform resource name (URN) (an attribute-value pair (AVP), 3GPP 29.214), a reservation priority (TS 183.017 [15]) (a vendor ID shall be set to european telecommunications standards institute (ETSI) (13019) [15]), a subscription ID (RFC 4006 [14]) identifying a particular subscription (e.g. international mobile subscriber identity (IMSI), mobile subscriber integrated services digital network (MSISDN), etc.), and a flow description (an attribute-value pair (AVP), 3GPP 29.214).
- A flow description in an application quality of service (QoS) request message must comprise one of the following two directions: ‘in’ or ‘out’, whereas direction ‘in’ refers to an uplink (UL) IP flow and direction ‘out’ refers to a downlink (DL) IP flow. A flow description in an application quality of service (QoS) request message may also contain: a source and destination IP address (possibly masked), a protocol, and a source and destination port (a source port may be omitted to indicate that any source port is allowed). Lists and ranges may not be used to indicate source and/or destination ports.
- A quality of service (QoS) application profile ID in an application quality of service (QoS) request message indicates appropriate quality of service (QoS) information to send to a home policy and charging rules function (PCRF) 104.
- In accordance with the principles of the present invention, the quality of service (QoS)
server 100 performs application quality of service (QoS) request message validation in response to an application quality of service (QoS) request message received thereon, as portrayed instep 17 ofFIG. 3 . - During application quality of service (QoS) request message validation, the quality of service (QoS)
server 100 validates the application identifier, access credentials (e.g. a secret/password public key infrastructure (PKI) verification, etc.), and quality of service (QoS) application profile ID received in the application quality of service (QoS) request message, against application profiles maintained in a localapplication information database 220. The quality of service (QoS)server 100 validates the format and values of application quality of service (QoS) request message attributes in accordance with a 3GPP series 29.214 specification. - When application quality of service (QoS) request message validation is complete, the quality of service (QoS)
server 100 queries a local mobile network operator (MNO)information database 230 to retrieve home mobile network operator (MNO) information for the requesting over-the-top (OTT)application client device 108, as depicted instep 18. If the quality of service (QoS)server 100 cannot find home mobile network operator (MNO) information for the requestingclient device 108 in the local mobile network operator (MNO)information database 230, then the quality of service (QoS)server 100 alternatively queries an external number portability database (NPDB) 270 via a number portability database (NPDB)interface 240. Results from either the number portability database (NPDB) 270 or the local mobile network operator (MNO)information database 230 provide the quality of service (QoS)server 100 with enough information to determine a home mobile network operator (MNO) for the requestingclient device 108. - Once a home mobile network operator (MNO) is identified (step 19), the quality of service (QoS)
server 100 uses a quality of service (QoS) application profile ID, defined in the application quality of service (QoS) request message, to determine whether or not the requesting over-the-top (OTT) application is authorized to influence quality of service (QoS) treatment on the home mobile network operator (MNO). - In
step 20 ofFIG. 3 , if the over-the-top (OTT) application is permitted to influence quality of service (QoS) settings on the home mobile network operator (MNO), then the quality of service (QoS)server 100 queries a local virtual private network (VPN)tunneling information database 250 to determine actual IP packet information associated with application data routed by the over-the-top (OTT) application over the virtual private network (VPN) tunnel 114. - In
step 21 ofFIG. 3 , the quality of service (QoS)server 100 sends a diameter authentication/authorization request (AAR) message with appropriate quality of service (QoS) information and appropriate IP tunneling data to a policy and charging rules function (PCRF) 104 on the client devices' 108 home mobile network operator (MNO). Appropriate quality of service (QoS) information depends on the type of virtual private network (VPN) tunnel 114 routing data. - In particular, if the virtual private network (VPN) tunnel 114 is a single-tenant virtual private network (VPN)
tunnel 520, then the diameter authentication/authorization request (AAR) message assigns quality of service (QoS) rules defined in the application quality of service (QoS) request message to all application data routed over the virtual private network (VPN) tunnel 114, as previously described in steps 11-13. This assignment allows mapping to the application quality of service (QoS) request message. - Rather, if the virtual private network (VPN) tunnel 114 is a multi-tenant virtual private network (VPN)
tunnel 500, then the quality of service (QoS)server 100 assigns quality of service (QoS) rules defined in the application quality of service (QoS) request message to application data being routed for the requesting over-the-top (OTT) application, only. In particular, the quality of service (QoS)server 100 sends a diameter authentication/authorization request (AAR) message with appropriate quality of service (QoS) rules and appropriate tunnel packet identification information to a policy and charging rules function (PCRF) 104 on theclient devices 108 home mobile network operator (MNO). Tunnel packet identification information sent to the policy and charging rules function (PCRF) must enable the policy and charging rules function (PCRF) to identify which tunnel packets to assign the requested quality of service (QoS) designation. - As portrayed in
step 22, the policy and charging rules function (PCRF) 104 on the client devices' 108 home mobile network operator (MNO) receives quality of service (QoS) information and returns a diameter authentication/authorization answer (AAA) message to the quality of service (QoS)server 100. - In
step 23, the quality of service (QoS)server 100 sends a quality of service (QoS) application response message with an appropriate status value to the over-the-top (OTT)application server 110. - In accordance with the principles of the present invention, a quality of service (QoS) application response message preferably comprises: a message ID, an application identifier, and a status identifier.
- A status identifier included in a status field of a quality of service (QoS) application response message may be any one or more of the following: a success status identifier (100), a quality of service (QoS) system failure status identifier (200) (indicating a default failure or unexpected failure with no available details), a failed validation of application identifier/access credentials status identifier (201), a failed validation of quality of service (QoS) profile ID status identifier (202), a quality of service (QoS) system failure reserved message status identifier (defined per quality of service (QoS) implementation and used to explain a unique system failure) (203-299), a PCRF unavailable status identifier (300), and/or an AAR/AAA message failure status identifier (400), wherein the entire contents of the AAA message is embedded in the status field.
- Once quality of service (QoS) rules have been forwarded to the policy and charging rules function (PCRF) 104 on the client devices' 108 home mobile network operator (MNO), the over-the-top (OTT)
application client 120 can proceed to transmit and consume data for service delivery purposes (i.e. the over-the-top (OTT)client 120 delivers a service as available to its' functionality and thereby consumes IP bandwidth as a result of service fulfillment). In particular, as depicted insteps 24 a and 24 b ofFIG. 3 , the over-the-top (OTT)application client 120 on theuser equipment 108 either initiates or receives a request to begin service fulfillment. - As shown in
step 25, once a request for service fulfillment is received (or initiated) on the over-the-top (OTT) application server 110 (via a Gi/SGi interface 310), the over-the-top (OTT)application server 110 attempts to establish a mutually authenticated (client 120 and server 110) transport layer security (TLS)/secure sockets layer (SSL) connection with the quality of service (QoS) server 100 (following standard transport layer security (TLS)/secure sockets layer (SSL) procedures for mutual authentication). - As portrayed in
step 26, if the initial mutual authentication step is successful, the over-the-top (OTT)application server 110 sends an application quality of service (QoS) request message over the virtual private network (VPN) tunnel 114 to the quality of service (QoS)server 100, to request that a desired level of quality of service (QoS) treatment be applied to application data routed by the over-the-top (OTT) application over the virtual private network (VPN) tunnel 114. - As depicted in steps 27-33, the quality of service (QoS)
server 100 then performs application quality of service (QoS) request message validation on the received application quality of service (QoS) request message, identifies a home mobile network operator (MNO) for the requesting client user equipment (UE) 108, sends appropriate quality of service (QoS) data to a home policy and charging rules function (PCRF) 104 based on the type of virtual private network (VPN) tunnel 114 routing application data, and subsequently forwards a quality of service (QoS) application response message to the over-the-top (OTT)application server 110, as previously described in steps 17-23. - In accordance with the principles of the present invention, once signaling or data services are terminated on the over-the-top (OTT)
application client device 108, the over-the-top (OTT)application server 110 informs the quality of service (QoS)server 100 of the service termination, to trigger reserved quality of service (QoS) values to be terminated on the client devices' 108 home mobile network operator (MNO). - In particular, as depicted in step 34 of
FIG. 3 , when the over-the-top (OTT)application server 110 detects a termination of signaling or service on the over-the-top (OTT) application client user equipment (UE) 108, the over-the-top (OTT)application server 110 attempts to establish a mutually authenticated (client 120 and server 110) TLS/SSL connection with the quality of service (QoS) server 100 (following standard TLS/SSL procedures for mutual authentication). - As portrayed in
step 35, if the initial mutual authentication step is successful, the over-the-top (OTT)application server 110 sends an application quality of service (QoS) termination message to the quality of service (QoS)server 100. - In accordance with the principles of the present invention, an application quality of service (QoS) termination message preferably includes: a message ID (an identifier defined by, and unique to, a requesting over-the-top (OTT) application), an application identifier (as described in 3GPP series 29.214 specification), access credentials (e.g. a secret/password public key infrastructure (PKI) verification, etc.), a quality of service (QoS) application profile ID, a source framed IP address (an attribute-value part (AVP)) or framed IPv6 prefix (an attribute-value part (AVP), RFC 4005 [12]), a service uniform resource name (URN) (an attribute-value part (AVP), 3GPP 29.214), a reservation priority (TS 183.017 [15]) (a vendor is preferably set to european telecommunications standards institute (ETSI) (13019) [15]), and a subscription ID (RFC 4006 [14]), identifying a particular subscription, e.g., international mobile subscriber identity (IMSI), mobile station integrated services digital network (MSISDN), etc.
- In response to an application quality of service (QoS) termination message, the quality of service (QoS)
server 100 performs application quality of service (QoS) termination message validation, as portrayed instep 36. During application quality of service (QoS) termination message validation, the quality of service (QoS)server 100 validates the application identifier and access credentials (e.g., a secret/password public key infrastructure (PKI) verification, etc.) received in the application quality of service (QoS) termination message against application profile data maintained in a localapplication information database 220. - As depicted in
step 37, once application quality of service (QoS) termination message validation is complete, the quality of service (QoS)server 100 sends a diameter session termination request (STR) message to the policy and charging rules function (PCRF) 104 on the over-the-top (OTT) application client device's 108 home mobile network operator (MNO), to indicate that service/signaling has been terminated. - In
steps server 100 with a diameter session termination answer (STA) message, and the quality of service (QoS)server 100 subsequently sends an application quality of service (QoS) response message (including an appropriate status value) to the requesting over-the-top (OTT)application server 110. - Similarly, the virtual private network (VPN)
client 118 and/orserver 112 sends an IPSec tunnel mapping table, containing appropriate tunnel termination information (tunneling information depicted in Table 1) to the quality of service (QoS)server 100, once the virtual private network (VPN) tunnel 114 is terminated. - In particular, as depicted in
steps client 118/server 112 sends a VPN quality of service (QoS) termination message with appropriate tunneling information (tunneling information depicted in Table 1) to the quality of service (QoS)server 100 when the virtual private network (VPN) tunnel 114 is terminated. The virtual private network (VPN)client 118 sends a VPN quality of service (QoS) termination message to the quality of service (QoS)server 100 via a conventional Gi/SGi interface 310. - In accordance with the principles of the present invention, a VPN quality of service (QoS) termination message preferably includes access credentials and a tunnel source and destination IP address, to enable the quality of service (QoS) server to identify which tunnel is being terminated and to determine if a pending quality of service (QoS) configuration in the wireless network need be removed as a result of the tunnel termination. A quality of service (QoS) termination message is typically preceded by a session termination. However, this may not always be the case.
- In step 41, the quality of service (QoS)
server 100 receives the VPN quality of service (QoS) termination message and appropriately responds to the virtual private network (VPN)client 118/server 112 with a VPN quality of service (QoS) response message. - Many commercial wireless networks provide quality of service (QoS) to their clients. The inventive solution is described herein via use of a specific long term evolution (LTE) network provider. However, the present invention may be applied to any wireless network that supports quality of service (QoS) treatment, including: a universal mobile telecommunications system (UMTS), long term evolution (LTE) technology, an evolved-universal mobile telecommunications system (E-UMTS), long term evolution (LTE) technology advanced, and Wi-Fi.
- Inventive quality of service (QoS) logic may and should be extended to support other scenarios, such as scenarios described as “Application Function” logic in 3GPP series 29 specifications.
- Use of this inventive technology causes certain packets associated with a virtual private network (VPN) connection to be identified via their security parameter index (SPI) value. Identification of this nature may reveal an associative characteristic of some virtual private network (VPN) packets. Implementers of the inventive technology may wish to determine if additional security, additional encryption, etc., is required to compensate for the reveal of the associative nature of packets.
- The present invention has particular applicability to United States federal agencies, such as the Federal Emergency Management Agency (FEMA), and the Department of Homeland Security (DHS), etc., as well as to emergency first responders, large over-the-top (OTT) application providers (e.g., Google™, Apple™, etc.), and enhanced long term evolution (LTE) policy and charging rules function(s) (PCRF), from policy and charging rules function (PCRF) vendors.
- While the invention has been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments of the invention without departing from the true spirit and scope of the invention.
Claims (21)
1-49. (canceled)
50. A method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a virtual private network (VPN) tunnel, comprising:
receiving a VPN quality of service (QoS) request message from an over-the-top (OTT) application server;
performing validation on said VPN quality of service (QoS) request message;
determining that said over-the-top (OTT) application server is permitted to change a quality of service (QoS) setting on a home mobile network operator (MNO) server;
tracking virtual private network (VPN) tunneling information received with said VPN quality of service (QoS) request message;
overriding current quality of service (QoS) rules with quality of service (QoS) rules embedded in said VPN quality of service (QoS) request message; and
routing a message to a policy and charging rules (PCRF) server to assign quality of service (QoS) rules defined in said VPN quality of service (QoS) request message to all application data routed over said virtual private network (VPN) tunnel;
wherein said virtual private network (VPN) tunnel is a single-tenant virtual private network (VPN) tunnel.
51. The method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a virtual private network (VPN) tunnel according to claim 50 , further comprising:
querying an external number portability database (NPDB) for home mobile network operator (MNO) information when home mobile network operator (MNO) information cannot be found by said home mobile network operator (MNO) server.
52. The method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a virtual private network (VPN) tunnel according to claim 50 , wherein:
said policy and charging rules function (PCRF) server provides conventional quality of service (QoS) treatment to said over-the-top (OTT) application transmitting data over said virtual private network (VPN) tunnel.
53. The method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a virtual private network (VPN) tunnel according to claim 50 , further comprising:
transmitting said quality of service information to said policy and charging rules function (PCRF) via a diameter protocol interface.
54. The method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a virtual private network (VPN) tunnel according to claim 50 , further comprising:
forwarding, via said policy and charging rules function (PCRF) on said home mobile network operator (MNO), received quality of service (QoS) rules to a policy and charging rules function (PCRF) serving said over-the-top (OTT) application client device when said (OTT) application client device is roaming.
55. The method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a virtual private network (VPN) tunnel according to claim 50 , wherein:
said VPN quality of service (QoS) request message indicates a particular quality of service (QoS) profile to invoke.
56. The method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a virtual private network (VPN) tunnel according to claim 50 , wherein:
said over-the-top (OTT) application server sends an application quality of service (QoS) termination message to said quality of service (QoS) server when said over-the-top (OTT) application server detects at least one of a termination of service, and a termination of signaling, on an over-the-top (OTT) application client device.
57. The method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a virtual private network (VPN) tunnel according to claim 56 , wherein:
said application quality of service (QoS) termination message indicates to said quality of service (QoS) server that reserved quality of service (QoS) values may be terminated on said home mobile network operator (MNO) assigned to said over-the-top (OTT) application client device.
58. A method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a virtual private network (VPN) tunnel, comprising:
receiving a VPN quality of service (QoS) request message from an over-the-top (OTT) application server;
performing validation on said VPN quality of service (QoS) request message;
determining that said over-the-top (OTT) application is permitted to change a quality of service (QoS) setting on a home mobile network operator (MNO) server;
tracking virtual private network (VPN) tunneling information received with said VPN quality of service (QoS) request message;
overriding current quality of service (QoS) rules with quality of service (QoS) rules embedded in said VPN quality of service (QoS) request message; and
routing a message to a policy and charging rules (PCRF) server to assign quality of service (QoS) rules defined in said VPN quality of service (QoS) request message to all application data routed for said requesting over-the-top (OTT) application;
wherein said virtual private network (VPN) tunnel is a multi-tenant virtual private network (VPN) tunnel.
59. The method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a virtual private network (VPN) tunnel according to claim 58 , further comprising:
querying an external number portability database (NPDB) for home mobile network operator (MNO) information when home mobile network operator (MNO) information cannot be found by said home mobile network operator (MNO) server.
60. The method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a multi-tenant virtual private network (VPN) tunnel according to claim 58 , wherein:
said policy and charging rules function (PCRF) server provides conventional quality of service (QoS) treatment to said over-the-top (OTT) application transmitting data over said virtual private network (VPN) tunnel.
61. The method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a multi-tenant virtual private network (VPN) tunnel according to claim 58 , further comprising:
transmitting said quality of service information to said policy and charging rules function (PCRF) via a diameter protocol interface.
62. The method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a multi-tenant virtual private network (VPN) tunnel according to claim 58 , further comprising:
forwarding, via said policy and charging rules function (PCRF) on said home mobile network operator (MNO), received quality of service (QoS) rules to a policy and charging rules function (PCRF) serving said over-the-top (OTT) application client device when said (OTT) application client device is roaming.
63. The method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a multi-tenant virtual private network (VPN) tunnel according to claim 58 , wherein:
said VPN quality of service (QoS) request message indicates a particular quality of service (QoS) profile to invoke.
64. The method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a multi-tenant virtual private network (VPN) tunnel according to claim 58 , wherein:
said over-the-top (OTT) application server sends an application quality of service (QoS) termination message to said quality of service (QoS) server when said over-the-top (OTT) application server detects at least one of a termination of service, and a termination of signaling, on an over-the-top (OTT) application client device.
65. The method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a multi-tenant virtual private network (VPN) tunnel according to claim 64 , wherein:
said application quality of service (QoS) termination message indicates to said quality of service (QoS) server that reserved quality of service (QoS) values may be terminated on said home mobile network operator (MNO) assigned to said over-the-top (OTT) application client device.
66. A method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a virtual private network (VPN) tunnel, comprising:
receiving a VPN quality of service (QoS) request message from an over-the-top (OTT) application server;
performing validation on said VPN quality of service (QoS) request message;
determining that said over-the-top (OTT) application is permitted to change a quality of service (QoS) setting on a home mobile network operator (MNO) server;
tracking virtual private network (VPN) tunneling information received with said VPN quality of service (QoS) request message;
overriding current quality of service (QoS) rules with quality of service (QoS) rules embedded in said VPN quality of service (QoS) request message; and
routing a message to a policy and charging rules (PCRF) server to assign quality of service (QoS) rules defined in said VPN quality of service (QoS) request message to all application data routed for said requesting over-the-top (OTT) application;
wherein said virtual private network (VPN) tunnel is a multi-tenant virtual private network (VPN) tunnel.
67. A method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a virtual private network (VPN) tunnel according to claim 66 , further comprising:
querying an external number portability database (NPDB) for home mobile network operator (MNO) information when home mobile network operator (MNO) information cannot be found by said home mobile network operator (MNO) server.
68. A method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a virtual private network (VPN) tunnel according to claim 66 , further comprising:
transmitting said quality of service information to said policy and charging rules function (PCRF) via a diameter protocol interface.
69. A method for extending quality of service (QoS) treatment to an over-the-top (OTT) application transmitting data over a commercial wireless network via a virtual private network (VPN) tunnel according to claim 66 , further comprising:
forwarding, via said policy and charging rules function (PCRF) on said home mobile network operator (MNO), received quality of service (QoS) rules to a policy and charging rules function (PCRF) serving said over-the-top (OTT) application client device when said (OTT) application client device is roaming.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/042,203 US20160165480A1 (en) | 2009-05-01 | 2016-02-12 | Quality of Service to Over the Top Applications Used with VPN |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17494409P | 2009-05-01 | 2009-05-01 | |
US201361815976P | 2013-04-25 | 2013-04-25 | |
US201361829745P | 2013-05-31 | 2013-05-31 | |
US14/032,913 US20140160990A1 (en) | 2012-09-20 | 2013-09-20 | Mechanisms for Quality of Service to Over the Top Applications for Use in Commercial Wireless Networks |
US14/056,412 US9301191B2 (en) | 2013-09-20 | 2013-10-17 | Quality of service to over the top applications used with VPN |
US15/042,203 US20160165480A1 (en) | 2009-05-01 | 2016-02-12 | Quality of Service to Over the Top Applications Used with VPN |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/056,412 Continuation US9301191B2 (en) | 2009-05-01 | 2013-10-17 | Quality of service to over the top applications used with VPN |
Publications (1)
Publication Number | Publication Date |
---|---|
US20160165480A1 true US20160165480A1 (en) | 2016-06-09 |
Family
ID=52690838
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/056,412 Expired - Fee Related US9301191B2 (en) | 2009-05-01 | 2013-10-17 | Quality of service to over the top applications used with VPN |
US14/953,758 Abandoned US20160192232A1 (en) | 2012-10-17 | 2015-11-30 | Quality of Service to Over the Top Applications Used with VPN |
US15/042,203 Abandoned US20160165480A1 (en) | 2009-05-01 | 2016-02-12 | Quality of Service to Over the Top Applications Used with VPN |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/056,412 Expired - Fee Related US9301191B2 (en) | 2009-05-01 | 2013-10-17 | Quality of service to over the top applications used with VPN |
US14/953,758 Abandoned US20160192232A1 (en) | 2012-10-17 | 2015-11-30 | Quality of Service to Over the Top Applications Used with VPN |
Country Status (1)
Country | Link |
---|---|
US (3) | US9301191B2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160119165A1 (en) * | 2014-10-27 | 2016-04-28 | Netsnapper Technologies Sarl | Methods and systems to manage network connections |
US11765050B1 (en) | 2022-03-15 | 2023-09-19 | Cisco Technology, Inc. | Event triggered guaranteed service connectivity |
Families Citing this family (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140160990A1 (en) * | 2012-09-20 | 2014-06-12 | Telecommunication Systems, Inc. | Mechanisms for Quality of Service to Over the Top Applications for Use in Commercial Wireless Networks |
US9609492B2 (en) * | 2013-10-17 | 2017-03-28 | Openet Telecom Ltd. | Method and system for dynamically creating tunnels suitable for metering and managing usage data for applications and services |
US9615260B2 (en) * | 2014-06-02 | 2017-04-04 | Intel Corporation | Adaptive quality of service for wireless networks |
US9794266B2 (en) | 2014-09-05 | 2017-10-17 | Qualcomm Incorporated | Using multiple credentials for access and traffic differentiation |
US10321361B2 (en) * | 2014-10-10 | 2019-06-11 | Huawei Technologies Co., Ltd. | Method and device for requesting a quality of experience in a communications network |
WO2016123919A1 (en) * | 2015-02-06 | 2016-08-11 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and network entity for qos control |
US9930591B2 (en) | 2015-03-02 | 2018-03-27 | Samsung Electronics Co., Ltd. | Method and apparatus for providing service in wireless communication system |
EP3089427B1 (en) * | 2015-04-27 | 2023-09-06 | Vodafone Holding GmbH | Controlling data exchange between a mobile communication network and a data provider |
US10447740B2 (en) * | 2015-07-14 | 2019-10-15 | Tata Communications (America) Inc. | System and method for call termination via an over-the-top (OTT) call service, based on connection characteristics |
US10051000B2 (en) * | 2015-07-28 | 2018-08-14 | Citrix Systems, Inc. | Efficient use of IPsec tunnels in multi-path environment |
EP3332577B1 (en) * | 2015-08-07 | 2020-04-29 | Samsung Electronics Co., Ltd. | Terminal and communication method of the same |
CN105119778B (en) * | 2015-09-09 | 2018-09-07 | 华为技术有限公司 | The method and apparatus for measuring time delay |
EP3440545A1 (en) * | 2016-04-05 | 2019-02-13 | Telefonaktiebolaget LM Ericsson (PUBL) | Method and agent for sharing information about cloudlet properties in distributed cloud environments |
US10129867B2 (en) * | 2016-04-29 | 2018-11-13 | At&T Intellectual Property I, L.P. | Universal peer-to-peer signaling network virtualization and orchestration |
US10015097B2 (en) | 2016-08-19 | 2018-07-03 | Oracle International Corporation | Fast access telecommunication tunnel cloning |
US10080171B2 (en) | 2016-12-14 | 2018-09-18 | T-Mobile Usa, Inc. | Continuous communication for prioritized user device applications |
US10425342B2 (en) * | 2016-12-16 | 2019-09-24 | Oracle International Corporation | Methods, systems, and computer readable media for priority routing of diameter messages |
US10673649B2 (en) * | 2017-10-24 | 2020-06-02 | Cisco Technology, Inc. | Method and device for quality of service regulation |
US10320643B2 (en) * | 2017-11-10 | 2019-06-11 | Netscout Systems, Inc. | Cloud computing environment system for automatically determining over-the-top applications and services |
US10630569B2 (en) * | 2017-11-10 | 2020-04-21 | Netscout Systems, Inc | Automatically determining over-the-top applications and services |
US11134410B2 (en) * | 2017-12-25 | 2021-09-28 | Nokia Solutions And Networks Oy | Quality of service (QoS) control in mobile edge computing (MEC) |
WO2019130047A1 (en) * | 2017-12-28 | 2019-07-04 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and system for enabling broadband roaming services |
US11394691B2 (en) * | 2018-06-05 | 2022-07-19 | Acreto Cloud Corporation | Ecosystem per distributed element security through virtual isolation networks |
US11683308B2 (en) * | 2019-06-06 | 2023-06-20 | Cisco Technology, Inc. | Systems and methods for generating contextual labels |
US20220247719A1 (en) * | 2019-09-24 | 2022-08-04 | Pribit Technology, Inc. | Network Access Control System And Method Therefor |
TWI742962B (en) * | 2020-01-07 | 2021-10-11 | 華碩電腦股份有限公司 | Method and apparatus for requesting sidelink transmission resources in a wireless communication system |
US11329883B2 (en) * | 2020-03-12 | 2022-05-10 | Fortinet, Inc. | Dynamic establishment of application-specific network tunnels between network devices by an SDWAN controller |
WO2021210278A1 (en) * | 2020-04-13 | 2021-10-21 | 株式会社Nttドコモ | Management device |
US11936522B2 (en) * | 2020-10-14 | 2024-03-19 | Connectify, Inc. | Selecting and operating an optimal virtual private network among multiple virtual private networks |
EP4120726A1 (en) * | 2021-07-15 | 2023-01-18 | Deutsche Telekom AG | Method for traffic management in a wireless network system |
WO2024038314A1 (en) * | 2022-08-15 | 2024-02-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and devices for application traffic flows |
Citations (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070258575A1 (en) * | 2006-05-05 | 2007-11-08 | John Douglas | Number portability for an IMS network |
US7561586B2 (en) * | 2003-09-19 | 2009-07-14 | Nortel Networks Limited | Method and apparatus for providing network VPN services on demand |
US20110219431A1 (en) * | 2010-03-04 | 2011-09-08 | Haseeb Akhtar | System and method of quality of service enablement for over the top applications in a telecommunications system |
US20110280143A1 (en) * | 2010-05-13 | 2011-11-17 | Futurewei Technologies, Inc. | System, Apparatus for Content Delivery for Internet Traffic and Methods Thereof |
US8089986B2 (en) * | 2003-05-15 | 2012-01-03 | At&T Intellectual Property I, L.P. | Managing quality of service in a communication network for applications |
US20120296784A1 (en) * | 2011-05-20 | 2012-11-22 | Brenda Ann Connor | Controlling quality of service provided to over the top applications in a telecommunications system |
US20120314632A1 (en) * | 2010-02-16 | 2012-12-13 | Pablo Martinez De La Cruz | Facilitating a communication session |
US20120324100A1 (en) * | 2011-04-13 | 2012-12-20 | Interdigital Patent Holdings, Inc | Methods, systems and apparatus for managing and/or enforcing policies for managing internet protocol ("ip") traffic among multiple accesses of a network |
US20130121262A1 (en) * | 2011-11-15 | 2013-05-16 | Motorola Solutions, Inc. | Preserving user-differentiated quality of service for mobile virtual private network communications made using a shared connection point |
US20130132854A1 (en) * | 2009-01-28 | 2013-05-23 | Headwater Partners I Llc | Service Plan Design, User Interfaces, Application Programming Interfaces, and Device Management |
US8504687B2 (en) * | 2008-11-26 | 2013-08-06 | Telecom Italia S.P.A. | Application data flow management in an IP network |
US20140020060A1 (en) * | 2012-07-12 | 2014-01-16 | Verizon Patent And Licensing Inc. | Quality of service application |
US20150043350A1 (en) * | 2012-03-14 | 2015-02-12 | Telefonaktiebolaget L M Ericsson (Publ) | Method for providing a qos prioritized data traffic |
Family Cites Families (643)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US1103073A (en) | 1912-07-18 | 1914-07-14 | American Telephone & Telegraph | Emergency signaling system for telephone toll-collecting apparatus. |
US4445118A (en) | 1981-05-22 | 1984-04-24 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | Navigation system and method |
US4651156A (en) | 1982-02-08 | 1987-03-17 | Mcgraw-Edison Co. | Integrated radio location and communication system |
US4494119A (en) | 1983-08-04 | 1985-01-15 | 122923 Canada Limited | Distress radiolocation method and system |
US4706275A (en) | 1985-11-13 | 1987-11-10 | Aerotel Ltd. | Telephone system |
DE3639753A1 (en) | 1986-11-21 | 1988-06-01 | Inst Rundfunktechnik Gmbh | METHOD FOR TRANSMITTING DIGITALIZED SOUND SIGNALS |
US4891638A (en) | 1987-10-30 | 1990-01-02 | Motorola, Inc. | Nationwide display pager with location readout |
US4891650A (en) | 1988-05-16 | 1990-01-02 | Trackmobile Inc. | Vehicle location system |
US5055851A (en) | 1988-05-16 | 1991-10-08 | Trackmobile, Inc. | Vehicle location system |
US5177478A (en) | 1988-06-24 | 1993-01-05 | Kabushiki Kaisha Toshiba | Paging system having an effective ID-code transferring function |
US5014206A (en) | 1988-08-22 | 1991-05-07 | Facilitech International Incorporated | Tracking system |
US4952928A (en) | 1988-08-29 | 1990-08-28 | B. I. Incorporated | Adaptable electronic monitoring and identification system |
CA1333296C (en) | 1988-11-15 | 1994-11-29 | Dawn Smith | Group emergency call system |
US4910767A (en) | 1989-01-03 | 1990-03-20 | Zenith Electronics Corporation | ANI auto dialer with carrier current interface |
US5081667A (en) | 1989-05-01 | 1992-01-14 | Clifford Electronics, Inc. | System for integrating a cellular telephone with a vehicle security system |
US5068891A (en) | 1989-05-31 | 1991-11-26 | Marshall Marvin E | Credit control system for long distance telephone services |
NL9000338A (en) | 1989-06-02 | 1991-01-02 | Koninkl Philips Electronics Nv | DIGITAL TRANSMISSION SYSTEM, TRANSMITTER AND RECEIVER FOR USE IN THE TRANSMISSION SYSTEM AND RECORD CARRIED OUT WITH THE TRANSMITTER IN THE FORM OF A RECORDING DEVICE. |
US5539829A (en) | 1989-06-02 | 1996-07-23 | U.S. Philips Corporation | Subband coded digital transmission system using some composite signals |
US5454024A (en) | 1989-08-31 | 1995-09-26 | Lebowitz; Mayer M. | Cellular digital packet data (CDPD) network transmission system incorporating cellular link integrity monitoring |
US5214789A (en) | 1989-11-17 | 1993-05-25 | Uniden America Corporation | Radio channel allocation based on location of mobile users |
US5239670A (en) | 1989-11-30 | 1993-08-24 | Motorola, Inc. | Satellite based global paging system |
US5070329A (en) | 1989-12-04 | 1991-12-03 | Motorola, Inc. | On-site communication system with rf shielding having pager identification capability |
US5610815A (en) | 1989-12-11 | 1997-03-11 | Caterpillar Inc. | Integrated vehicle positioning and navigation system, apparatus and method |
US5283570A (en) | 1989-12-14 | 1994-02-01 | Motorola, Inc. | Multiple format signalling protocol for a selective call receiver |
US5193215A (en) | 1990-01-25 | 1993-03-09 | Olmer Anthony L | Location signalling device for automatically placing a radio distress call |
US5640323A (en) | 1990-02-05 | 1997-06-17 | Caterpillar Inc. | System and method for operating an autonomous navigation system |
IT1248151B (en) | 1990-04-27 | 1995-01-05 | Scandic Int Pty Ltd | INTELLIGENT PAPER VALIDATION DEVICE AND METHOD |
US5119104A (en) | 1990-05-04 | 1992-06-02 | Heller Alan C | Location system adapted for use in multipath environments |
US5144283A (en) | 1990-06-18 | 1992-09-01 | Kenneth P. Arens | Energy efficient alarm system and regulative central control unit |
GB9016277D0 (en) | 1990-07-25 | 1990-09-12 | British Telecomm | Location and handover in mobile radio systems |
US5239570A (en) | 1990-07-25 | 1993-08-24 | Teltone Corporation | 9-1-1 Switched access system |
US5043736B1 (en) | 1990-07-27 | 1994-09-06 | Cae Link Corp | Cellular position location system |
US5327529A (en) | 1990-09-24 | 1994-07-05 | Geoworks | Process of designing user's interfaces for application programs |
US5574648A (en) | 1990-10-09 | 1996-11-12 | Pilley; Harold R. | Airport control/management system using GNSS-based methods and equipment for the control of surface and airborne traffic |
IL95990A (en) | 1990-10-15 | 1994-07-31 | B V R Technologies Ltd | Anti-collision warning system |
US5161180A (en) | 1990-10-19 | 1992-11-03 | Chavous Robert O | Call interceptor for emergency systems |
US5293642A (en) | 1990-12-19 | 1994-03-08 | Northern Telecom Limited | Method of locating a mobile station |
US5068656A (en) | 1990-12-21 | 1991-11-26 | Rockwell International Corporation | System and method for monitoring and reporting out-of-route mileage for long haul trucks |
US5155689A (en) | 1991-01-17 | 1992-10-13 | By-Word Technologies, Inc. | Vehicle locating and communicating method and apparatus |
US5208756A (en) | 1991-01-28 | 1993-05-04 | Song Han L | Vehicle locating and navigating system |
US5126722A (en) | 1991-02-04 | 1992-06-30 | Lubriquip, Inc. | Point of lube monitor |
FI94581C (en) | 1991-02-12 | 1995-09-25 | Nokia Telecommunications Oy | System for automatically communicating contact information in a mobile telephone network or the like |
US5235630A (en) | 1991-04-17 | 1993-08-10 | Telident, Incorporated | Emergency call station identification system and method |
WO1993000647A2 (en) | 1991-06-21 | 1993-01-07 | Unitech Research, Inc. | Real time three dimensional geo-referenced digital orthophotograph-based positioning, navigation, collision avoidance and decision support system |
US5266944A (en) | 1991-06-26 | 1993-11-30 | Bodyguard Technologies, Inc. | Electronic system and method for monitoring abusers for compliance with a protective order |
US5265630A (en) | 1991-08-09 | 1993-11-30 | Robert Hartmann | Environmentally-friendly battery cleaning system |
US5289527A (en) | 1991-09-20 | 1994-02-22 | Qualcomm Incorporated | Mobile communications device registration method |
US5526404A (en) | 1991-10-10 | 1996-06-11 | Space Systems/Loral, Inc. | Worldwide satellite telephone system and a network coordinating gateway for allocating satellite and terrestrial gateway resources |
US5787357A (en) | 1991-10-17 | 1998-07-28 | Nokia Telecommunications Oy | Short message processing in a mobile exchange |
US5390339A (en) | 1991-10-23 | 1995-02-14 | Motorola Inc. | Method and apparatus for selecting a serving transceiver |
JPH05130019A (en) | 1991-11-08 | 1993-05-25 | Hitachi Ltd | Position registration system |
CA2079827C (en) | 1991-12-09 | 2003-08-19 | Theresa Chen Yen Wang | Mobile unit tracking system |
US6324404B1 (en) | 1991-12-26 | 2001-11-27 | Sycord Limited Partnership | Cellular telephone system that uses position of a mobile unit to make call management decisions |
US5546445A (en) | 1991-12-26 | 1996-08-13 | Dennison; Everett | Cellular telephone system that uses position of a mobile unit to make call management decisions |
SG43096A1 (en) | 1992-01-20 | 1997-10-17 | Nec Corp | Person location system |
US5334974A (en) | 1992-02-06 | 1994-08-02 | Simms James R | Personal security system |
SE469867B (en) | 1992-02-17 | 1993-09-27 | Ericsson Telefon Ab L M | Paging Procedure |
JP2900680B2 (en) | 1992-02-21 | 1999-06-02 | 日本電気株式会社 | Wireless telephone equipment |
FR2689668B1 (en) | 1992-04-07 | 1994-05-20 | Dassault Electronique | FIELD ANTI-COLLISION PROCESS AND DEVICE FOR AIRCRAFT. |
US5223844B1 (en) | 1992-04-17 | 2000-01-25 | Auto Trac Inc | Vehicle tracking and security system |
US5359529A (en) | 1992-05-15 | 1994-10-25 | Zexel Corporation | Route guidance on/off-route state filter |
US5311516A (en) | 1992-05-29 | 1994-05-10 | Motorola, Inc. | Paging system using message fragmentation to redistribute traffic |
US5218367A (en) | 1992-06-01 | 1993-06-08 | Trackmobile | Vehicle tracking system |
US5363425A (en) | 1992-06-29 | 1994-11-08 | Northern Telecom Limited | Method and apparatus for providing a personal locator, access control and asset tracking service using an in-building telephone network |
US5432841A (en) | 1992-07-10 | 1995-07-11 | Rimer; Neil A. | System for locating and communicating with mobile vehicles |
US5335246A (en) | 1992-08-20 | 1994-08-02 | Nexus Telecommunication Systems, Ltd. | Pager with reverse paging facility |
FI109064B (en) | 1992-09-18 | 2002-05-15 | Nokia Corp | A method for initiating short message transmission in a cellular radio system, a cellular radio system, and a subscriber register of a cellular radio system |
JP3673285B2 (en) | 1992-10-09 | 2005-07-20 | 櫻護謨株式会社 | Outdoor work automation system |
US5689245A (en) | 1992-10-19 | 1997-11-18 | Radio Satellite Corporation | Integrated communications terminal |
US5361212A (en) | 1992-11-02 | 1994-11-01 | Honeywell Inc. | Differential GPS landing assistance system |
US5418537A (en) | 1992-11-18 | 1995-05-23 | Trimble Navigation, Ltd. | Location of missing vehicles |
US5422813A (en) | 1992-12-17 | 1995-06-06 | Stanford Telecommunications, Inc. | No-outage GPS/commercial RF positioning system |
US5464899A (en) | 1992-12-30 | 1995-11-07 | Bridgestone Corporation | High modulus low hysteresis rubber compound for pneumatic tires |
FI92364C (en) | 1993-01-15 | 1994-10-25 | Nokia Telecommunications Oy | A method for initiating a short message transmission in a mobile telephone network and a home register of the mobile telephone system |
US5343493A (en) | 1993-03-16 | 1994-08-30 | Hughes Aircraft Company | Personal assistance system and method for use with a cellular communication system |
DE4312362A1 (en) | 1993-04-16 | 1994-10-20 | Sel Alcatel Ag | Mobile radio system with credit accounts |
US5604486A (en) | 1993-05-27 | 1997-02-18 | Motorola, Inc. | RF tagging system with multiple decoding modalities |
US5387993A (en) | 1993-06-25 | 1995-02-07 | Precision Tracking Fm, Inc. | Method for receiving and transmitting optical data and control information to and from remotely located receivers and transmitters in an optical locator system |
US5425077A (en) | 1993-07-08 | 1995-06-13 | U.S. West Advanced Technologies, Inc. | Mobile telephone user interface including fixed and dynamic function keys and method of using same |
JPH0750725A (en) | 1993-08-06 | 1995-02-21 | Sony Corp | System and method for managing information |
US5388147A (en) | 1993-08-30 | 1995-02-07 | At&T Corp. | Cellular telecommunication switching system for providing public emergency call location information |
US5479482A (en) | 1993-08-30 | 1995-12-26 | At&T Corp. | Cellular terminal for providing public emergency call location information |
US5497149A (en) | 1993-09-02 | 1996-03-05 | Fast; Ray | Global security system |
IL110891A (en) | 1993-09-14 | 1999-03-12 | Spyrus | System and method for data access control |
FI98687C (en) | 1993-09-20 | 1997-07-25 | Nokia Telecommunications Oy | A mobile communication system and method for connecting a remote workstation via a mobile communication network to a data network |
US5423076A (en) | 1993-09-24 | 1995-06-06 | Rockwell International Corporation | Superheterodyne tranceiver with bilateral first mixer and dual phase locked loop frequency control |
US5434789A (en) | 1993-10-06 | 1995-07-18 | Fraker; William F. | GPS golf diagnostic system |
US5543776A (en) | 1993-10-19 | 1996-08-06 | Whistler Corporation | Vehicle security system |
CA2134729C (en) | 1993-11-01 | 1999-09-07 | Thomas E. Buss | Location dependent information receiving device and method |
US5629693A (en) | 1993-11-24 | 1997-05-13 | Trimble Navigation Limited | Clandestine location reporting by a missing vehicle |
US5519403A (en) | 1993-11-29 | 1996-05-21 | Motorola, Inc. | Global positioning system communications multi-interface |
CA2135856A1 (en) | 1993-12-10 | 1995-06-11 | Steven Peter Allen | Low power, addressable data communication device and method |
US5552772A (en) | 1993-12-20 | 1996-09-03 | Trimble Navigation Limited | Location of emergency service workers |
US5568119A (en) | 1993-12-21 | 1996-10-22 | Trimble Navigation Limited | Arrestee monitoring with variable site boundaries |
US5614890A (en) | 1993-12-27 | 1997-03-25 | Motorola, Inc. | Personal identification system |
US5506886A (en) | 1993-12-27 | 1996-04-09 | Motorola, Inc. | Wide area paging with roaming subscriber units |
TW289174B (en) | 1994-01-07 | 1996-10-21 | Minnesota Mining & Mfg | |
US5535434A (en) | 1994-01-24 | 1996-07-09 | Motorola, Inc. | Carry case having paging circuitry section |
US5555286A (en) | 1994-01-31 | 1996-09-10 | Tendler Technologies, Inc. | Cellular phone based automatic emergency vessel/vehicle location system |
US5588009A (en) | 1994-02-03 | 1996-12-24 | Will; Craig A. | Personal paging, communications, and locating system |
US5479408A (en) | 1994-02-22 | 1995-12-26 | Will; Craig A. | Wireless personal paging, communications, and locating system |
US5661652A (en) | 1994-02-22 | 1997-08-26 | Trimble Navigation Limited | Mobile network with automatic position reporting between member units |
US5374936A (en) | 1994-02-28 | 1994-12-20 | Feng; Jun | Security system |
JP2786809B2 (en) | 1994-03-08 | 1998-08-13 | 株式会社トキメック | Ship navigation support device |
US5470233A (en) | 1994-03-17 | 1995-11-28 | Arkenstone, Inc. | System and method for tracking a pedestrian |
US5485163A (en) | 1994-03-30 | 1996-01-16 | Motorola, Inc. | Personal locator system |
DE4413451A1 (en) | 1994-04-18 | 1995-12-14 | Rolf Brugger | Device for the distribution of music information in digital form |
US5731785A (en) | 1994-05-13 | 1998-03-24 | Lemelson; Jerome H. | System and method for locating objects including an inhibiting feature |
US5704029A (en) | 1994-05-23 | 1997-12-30 | Wright Strategies, Inc. | System and method for completing an electronic form |
US5461390A (en) | 1994-05-27 | 1995-10-24 | At&T Ipm Corp. | Locator device useful for house arrest and stalker detection |
US5719926A (en) | 1994-06-10 | 1998-02-17 | Communications Product Development, Inc. | Prepaid long-distance telephone service system with flexible operating parameters |
US5802492A (en) | 1994-06-24 | 1998-09-01 | Delorme Publishing Company, Inc. | Computer aided routing and positioning system |
FI98688C (en) | 1994-07-20 | 1997-07-25 | Nokia Telecommunications Oy | Method for initiating a short message transmission in a cellular radio system, a cellular radio system and subscriber register in a cellular radio system |
US5530914A (en) | 1994-08-15 | 1996-06-25 | Motorola, Inc. | Method for determining when a radio leaves a radio talk group |
US5802479A (en) | 1994-09-23 | 1998-09-01 | Advanced Safety Concepts, Inc. | Motor vehicle occupant sensing systems |
US6169891B1 (en) | 1994-10-18 | 2001-01-02 | At&T Corp. | Method and apparatus for billing of wireless telephone calls |
AU697176B2 (en) | 1994-11-04 | 1998-10-01 | Koninklijke Philips Electronics N.V. | Encoding and decoding of a wideband digital information signal |
US5485161A (en) | 1994-11-21 | 1996-01-16 | Trimble Navigation Limited | Vehicle speed control based on GPS/MAP matching of posted speeds |
US6226529B1 (en) | 1994-12-08 | 2001-05-01 | Itt Manufacturing Enterprises, Inc. | System for providing a simultaneous data and voice channel within a single channel of a portable cellular telephone to provide position-enhanced cellular services (PECS) |
US5579372A (en) | 1994-12-12 | 1996-11-26 | Telefonaktiebolaget Lm Ericsson | Flow control method for short message service - busy subscriber |
US5761618A (en) | 1994-12-22 | 1998-06-02 | Bell Atlantic Mobile Systems, Inc. | Updating technique for downloading new system identification (SID) list into a handset |
US5532690A (en) | 1995-04-04 | 1996-07-02 | Itt Corporation | Apparatus and method for monitoring and bounding the path of a ground vehicle |
IL113259A (en) | 1995-04-05 | 2001-03-19 | Diversinet Corp | Apparatus and method for safe communication handshake and data transfer |
CA2172564C (en) | 1995-04-28 | 1999-12-28 | Mark Jeffrey Foladare | Call redirection system |
US5621793A (en) | 1995-05-05 | 1997-04-15 | Rubin, Bednarek & Associates, Inc. | TV set top box using GPS |
US5517199A (en) | 1995-05-11 | 1996-05-14 | Aerodata Corporation | Emergency locator device |
AU5848896A (en) | 1995-05-23 | 1996-12-11 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for supporting delivery of short messag e service messages to sleeping mobile stations in a cellular communications system |
US5568153A (en) | 1995-05-30 | 1996-10-22 | Telefonaktiebolaget Lm Ericsson | Individually defined personal home area for subscribers in a cellular telecommunications network |
US5797096A (en) | 1995-08-02 | 1998-08-18 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method for maintaining control channel mode information in a cellular telecommunications network |
SE9502995L (en) | 1995-08-30 | 1996-08-26 | Sendit Ab | Systems and host device for transmission of electronic mail over a mobile telephone network |
NL1001162C2 (en) | 1995-09-08 | 1997-03-11 | Nederland Ptt | Communication system for interactive services with a packet-switched interaction channel over a narrow-band circuit-switched network, as well as a device for application in such a communication system. |
US5721781A (en) | 1995-09-13 | 1998-02-24 | Microsoft Corporation | Authentication system and method for smart card transactions |
US5943399A (en) | 1995-09-29 | 1999-08-24 | Northern Telecom Limited | Methods and apparatus for providing communications to telecommunications terminals |
US5774670A (en) | 1995-10-06 | 1998-06-30 | Netscape Communications Corporation | Persistent client state in a hypertext transfer protocol based client-server system |
US5884214A (en) | 1996-09-06 | 1999-03-16 | Snaptrack, Inc. | GPS receiver and method for processing GPS signals |
US6131067A (en) | 1995-10-09 | 2000-10-10 | Snaptrack, Inc. | Client-server based remote locator device |
US6208290B1 (en) | 1996-03-08 | 2001-03-27 | Snaptrack, Inc. | GPS receiver utilizing a communication link |
US5663734A (en) | 1995-10-09 | 1997-09-02 | Precision Tracking, Inc. | GPS receiver and method for processing GPS signals |
US5841396A (en) | 1996-03-08 | 1998-11-24 | Snaptrack, Inc. | GPS receiver utilizing a communication link |
US6633255B2 (en) | 1995-10-09 | 2003-10-14 | Qualcomm Inc. | Method for open loop tracking GPS signals |
US5806000A (en) | 1995-10-12 | 1998-09-08 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method for implementing short message service extension phones within a radio telecommunications network |
US6807534B1 (en) | 1995-10-13 | 2004-10-19 | Trustees Of Dartmouth College | System and method for managing copyrighted electronic media |
US5765152A (en) | 1995-10-13 | 1998-06-09 | Trustees Of Dartmouth College | System and method for managing copyrighted electronic media |
US5771353A (en) | 1995-11-13 | 1998-06-23 | Motorola Inc. | System having virtual session manager used sessionless-oriented protocol to communicate with user device via wireless channel and session-oriented protocol to communicate with host server |
US5946629A (en) | 1995-11-28 | 1999-08-31 | Telefonaktiebolaget L M Ericsson | Cellular telephone network having short message service interaction with other networks |
US5920821A (en) | 1995-12-04 | 1999-07-06 | Bell Atlantic Network Services, Inc. | Use of cellular digital packet data (CDPD) communications to convey system identification list data to roaming cellular subscriber stations |
US5809415A (en) | 1995-12-11 | 1998-09-15 | Unwired Planet, Inc. | Method and architecture for an interactive two-way data communication network |
US5835907A (en) | 1995-12-20 | 1998-11-10 | Mci Communications Corporation | Emergency PCS system for identification and notification of a subscriber's location |
US5794142A (en) | 1996-01-29 | 1998-08-11 | Nokia Mobile Phones Limited | Mobile terminal having network services activation through the use of point-to-point short message service |
US5740534A (en) | 1996-02-22 | 1998-04-14 | Motorola, Inc. | Method for determining available frequencies in selective call receivers |
FI102869B1 (en) | 1996-02-26 | 1999-02-26 | Nokia Mobile Phones Ltd | Device, method and system for transmitting and receiving information in connection with various applications |
US5945944A (en) | 1996-03-08 | 1999-08-31 | Snaptrack, Inc. | Method and apparatus for determining time for GPS receivers |
US6133874A (en) | 1996-03-08 | 2000-10-17 | Snaptrack, Inc. | Method and apparatus for acquiring satellite positioning system signals |
US6125325A (en) | 1996-04-25 | 2000-09-26 | Sirf Technology, Inc. | GPS receiver with cross-track hold |
US5901171A (en) | 1996-03-15 | 1999-05-04 | Sirf Technology, Inc. | Triple multiplexing spread spectrum receiver |
US6169901B1 (en) | 1996-03-27 | 2001-01-02 | U.S. Philips Corporation | Mobile telephone with interial identifier in location messages |
US5768509A (en) | 1996-04-08 | 1998-06-16 | Adc Newnet, Inc. | Short message server without local customer database |
US5822700A (en) | 1996-04-18 | 1998-10-13 | Telefonaktiebolaget L M Ericsson | Flow control of short message service messages in a cellular telephone network |
US6085320A (en) | 1996-05-15 | 2000-07-04 | Rsa Security Inc. | Client/server protocol for proving authenticity |
US5983099A (en) | 1996-06-11 | 1999-11-09 | Qualcomm Incorporated | Method/apparatus for an accelerated response to resource allocation requests in a CDMA push-to-talk system using a CDMA interconnect subsystem to route calls |
US5857201A (en) | 1996-06-18 | 1999-01-05 | Wright Strategies, Inc. | Enterprise connectivity to handheld devices |
US5960362A (en) | 1996-06-24 | 1999-09-28 | Qualcomm Incorporated | Method and apparatus for access regulation and system protection of a dispatch system |
US5812086A (en) | 1996-06-27 | 1998-09-22 | Motorola, Inc. | Method and apparatus for providing duplex communication service in geographical areas where conventional services are obstructed |
US5767795A (en) | 1996-07-03 | 1998-06-16 | Delta Information Systems, Inc. | GPS-based information system for vehicles |
US5746434A (en) | 1996-07-09 | 1998-05-05 | Lam Research Corporation | Chamber interfacing O-rings and method for implementing same |
US5946630A (en) | 1996-07-10 | 1999-08-31 | Telefonaktiebolaget L M Ericsson (Publ) | Method for storing and forwarding short messages to mobile subscribers in a cellular communications system |
US5774533A (en) | 1996-08-14 | 1998-06-30 | Bellsouth Corporation | Method and system for providing a billing directed communication service |
US6199045B1 (en) | 1996-08-15 | 2001-03-06 | Spatial Adventures, Inc. | Method and apparatus for providing position-related information to mobile recipients |
US6101378A (en) | 1996-08-15 | 2000-08-08 | Japan Radio Co., Ltd. | Pre-paid cellular telephone system |
US6185427B1 (en) | 1996-09-06 | 2001-02-06 | Snaptrack, Inc. | Distributed satellite position system processing and application network |
FI103546B (en) | 1996-09-16 | 1999-07-15 | Nokia Telecommunications Oy | Data service in a mobile telephone network |
KR19980021532A (en) | 1996-09-17 | 1998-06-25 | 유기범 | How to locate MS location in CDM personal mobile communication |
US6181935B1 (en) | 1996-09-27 | 2001-01-30 | Software.Com, Inc. | Mobility extended telephone application programming interface and method of use |
US6122503A (en) | 1996-10-08 | 2000-09-19 | At&T Wireless Services Inc | Method and apparatus for over-the-air programming of telecommunication services |
US5930701A (en) | 1996-10-17 | 1999-07-27 | Telefonaktiebolaget L M Ericsson (Publ) | Providing caller ID within a mobile telecommunications network |
SE510664C2 (en) | 1996-10-29 | 1999-06-14 | Ericsson Telefon Ab L M | Methods and apparatus for message management in a communication system |
US6188752B1 (en) | 1996-11-12 | 2001-02-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for providing prepaid telecommunications services |
US5828740A (en) | 1996-11-14 | 1998-10-27 | Sprint Communications Co., L.P. | Prepaid calling card external/adjunct database processor |
US6249680B1 (en) | 1997-01-08 | 2001-06-19 | U.S. Wireless Corporation | Radio transmitter location finding in CDMA wireless communication systems |
US6456852B2 (en) | 1997-01-08 | 2002-09-24 | Trafficmaster Usa, Inc. | Internet distributed real-time wireless location database |
US6061346A (en) | 1997-01-17 | 2000-05-09 | Telefonaktiebolaget Lm Ericsson (Publ) | Secure access method, and associated apparatus, for accessing a private IP network |
US6064875A (en) | 1997-01-31 | 2000-05-16 | Usa Telecommunications Services, Inc. | Wireless communications system and method of operation for reducing fraud |
US5812087A (en) | 1997-02-03 | 1998-09-22 | Snaptrack, Inc. | Method and apparatus for satellite positioning system based time measurement |
US6215442B1 (en) | 1997-02-03 | 2001-04-10 | Snaptrack, Inc. | Method and apparatus for determining time in a satellite positioning system |
US6377209B1 (en) | 1997-02-03 | 2002-04-23 | Snaptrack, Inc. | Method and apparatus for satellite positioning system (SPS) time measurement |
US6058300A (en) | 1997-02-04 | 2000-05-02 | National Telemanagement Corporation | Prepay telecommunications system |
US5922074A (en) | 1997-02-28 | 1999-07-13 | Xcert Software, Inc. | Method of and apparatus for providing secure distributed directory services and public key infrastructure |
US6178505B1 (en) | 1997-03-10 | 2001-01-23 | Internet Dynamics, Inc. | Secure delivery of information in a network |
US5950130A (en) | 1997-03-18 | 1999-09-07 | Sbc Technology Resources, Inc. | Mobile station with intelligent roaming and over-the-air programming features |
US5998111A (en) | 1997-03-31 | 1999-12-07 | Fuji Photo Film Co., Ltd. | Process for producing photographic suspended processing agent composition |
US6169902B1 (en) | 1997-04-09 | 2001-01-02 | Sony Corporation | Information terminal, processing method by information terminal, information providing apparatus and information network system |
US6411254B1 (en) | 1997-04-15 | 2002-06-25 | Snaptrack, Inc. | Satellite positioning reference system and method |
US6215441B1 (en) | 1997-04-15 | 2001-04-10 | Snaptrack, Inc. | Satellite positioning reference system and method |
US5974054A (en) | 1997-04-23 | 1999-10-26 | Motorola, Inc. | Method and apparatus in a radio messaging system for forming a current frame of data while maintaining a correct transmission order for numbered messages |
DE19718654C2 (en) | 1997-05-02 | 1999-05-06 | Ericsson Telefon Ab L M | Communication system for electronic messages |
SE509435C2 (en) | 1997-05-16 | 1999-01-25 | Ericsson Telefon Ab L M | Privacy protection in a telecommunications system |
US6240294B1 (en) | 1997-05-30 | 2001-05-29 | Itt Manufacturing Enterprises, Inc. | Mobile radio device having adaptive position transmitting capabilities |
US6049710A (en) | 1997-06-19 | 2000-04-11 | Kimberley Nanette Engen | Wireless prepaid telephone system with dispensable instruments |
JP4145362B2 (en) | 1997-07-11 | 2008-09-03 | コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ | Apparatus for requesting individual use authentication for a regenerated encrypted information signal |
US6560461B1 (en) | 1997-08-04 | 2003-05-06 | Mundi Fomukong | Authorized location reporting paging system |
JPH1168873A (en) | 1997-08-08 | 1999-03-09 | Nec Corp | Method and system for data communication |
US6070085A (en) | 1997-08-12 | 2000-05-30 | Qualcomm Inc. | Method and apparatus for controlling transmit power thresholds based on classification of wireless communication subscribers |
US6680694B1 (en) | 1997-08-19 | 2004-01-20 | Siemens Vdo Automotive Corporation | Vehicle information system |
US6707421B1 (en) | 1997-08-19 | 2004-03-16 | Siemens Vdo Automotive Corporation | Driver information system |
US6108533A (en) | 1997-08-22 | 2000-08-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Geographical database for radio system |
FI113119B (en) | 1997-09-15 | 2004-02-27 | Nokia Corp | A method for securing communications over telecommunications networks |
FI106282B (en) | 1997-09-22 | 2000-12-29 | Nokia Networks Oy | A method and system for transmitting a short message over a telecommunications network |
US6075982A (en) | 1997-09-23 | 2000-06-13 | Mci Communications Corporation | Wireless prepaid platform integration with standard signaling |
US6531982B1 (en) | 1997-09-30 | 2003-03-11 | Sirf Technology, Inc. | Field unit for use in a GPS system |
US6070067A (en) | 1997-10-31 | 2000-05-30 | Telefonaktiebolaget Lm Ericsson | Prepayment method utilizing credit information stored in mobile terminals for accessing wireless telecommunication networks |
US6173181B1 (en) | 1997-11-07 | 2001-01-09 | Motorola, Inc. | Method and system for controlling neighbor scanning in a subscriber unit in a cellular communication system |
US6138003A (en) | 1997-11-26 | 2000-10-24 | Ericsson Inc. | System and method for authorization of location services |
US6032051A (en) | 1997-12-01 | 2000-02-29 | Telefonaktiebolaget L/M Ericsson | Wireless mobile comunication devices for group use |
US6397201B1 (en) | 1997-12-02 | 2002-05-28 | David W. Arathorn | E-cell (equivalent cell) and the basic circuit modules of e-circuits: e-cell pair totem, the basic memory circuit and association extension |
US6526026B1 (en) | 1997-12-10 | 2003-02-25 | Intel Corporation | Digit transmission over wireless communication link |
US6131028A (en) | 1997-12-10 | 2000-10-10 | Integrated Telecom Solutions, Inc. | Method of providing services specified by feature codes based upon location of a wireless telephone unit |
US5978685A (en) | 1997-12-15 | 1999-11-02 | Telefonaktiebolaget L/M Ericsson | Digital cellular telecommunications with short message service over the packet channel |
US6266614B1 (en) | 1997-12-24 | 2001-07-24 | Wendell Alumbaugh | Travel guide |
US6512930B2 (en) | 1997-12-30 | 2003-01-28 | Telefonaktiebolaget Lm Ericsson (Publ) | On-line notification in a mobile communications system |
US6035025A (en) | 1998-01-07 | 2000-03-07 | National Telemanagement Corporation | System and method for a prepaid bundled telecommunications account |
US6148342A (en) | 1998-01-27 | 2000-11-14 | Ho; Andrew P. | Secure database management system for confidential records using separately encrypted identifier and access request |
US6275692B1 (en) | 1998-02-11 | 2001-08-14 | Telefonaktiebolaget L M Ericsson (Publ) | Server request including code for customizing service to requesting cellular mobile station |
US6122520A (en) | 1998-02-13 | 2000-09-19 | Xerox Corporation | System and method for obtaining and using location specific information |
US6081508A (en) | 1998-02-25 | 2000-06-27 | Indus River Networks, Inc. | Remote computer communication |
US6148197A (en) | 1998-03-06 | 2000-11-14 | Sbc Technology Resources, Inc. | Intelligent roaming system with over the air programming |
US6081229A (en) | 1998-03-17 | 2000-06-27 | Qualcomm Incorporated | System and method for determining the position of a wireless CDMA transceiver |
US6154172A (en) | 1998-03-31 | 2000-11-28 | Piccionelli; Gregory A. | System and process for limiting distribution of information on a communication network based on geographic location |
US6199113B1 (en) | 1998-04-15 | 2001-03-06 | Sun Microsystems, Inc. | Apparatus and method for providing trusted network security |
DE69830386T2 (en) | 1998-04-17 | 2005-11-24 | Motorola, Inc., Schaumburg | Data processing system and method therefor |
US6195557B1 (en) | 1998-04-20 | 2001-02-27 | Ericsson Inc. | System and method for use of override keys for location services |
US6104931A (en) | 1998-04-20 | 2000-08-15 | Ericsson Inc. | System and method for defining location services |
US5999124A (en) | 1998-04-22 | 1999-12-07 | Snaptrack, Inc, | Satellite positioning system augmentation with wireless communication signals |
BRPI9910049B1 (en) | 1998-04-28 | 2016-11-16 | Nokia Corp | method and network for controlling wireless session protocol (wsp) sessions |
US6421781B1 (en) | 1998-04-30 | 2002-07-16 | Openwave Systems Inc. | Method and apparatus for maintaining security in a push server |
US6061018A (en) | 1998-05-05 | 2000-05-09 | Snaptrack, Inc. | Method and system for using altitude information in a satellite positioning system |
US6816710B2 (en) | 1998-05-06 | 2004-11-09 | Snaptrack, Inc. | Method and apparatus for signal processing in a satellite positioning system |
US6208854B1 (en) | 1998-05-14 | 2001-03-27 | Ameritech Corporation | System and method for routing a call to a called party's landline or wireless communication unit |
US6313786B1 (en) | 1998-07-02 | 2001-11-06 | Snaptrack, Inc. | Method and apparatus for measurement processing of satellite positioning system (SPS) signals |
US6278701B1 (en) | 1998-07-10 | 2001-08-21 | Verizon Laboratories Inc. | Capacity enhancement for multi-code CDMA with integrated services through quality of services and admission control |
US6148198A (en) | 1998-08-05 | 2000-11-14 | Ericsson Inc. | Method and apparatus for selecting a service provider |
US6289373B1 (en) | 1998-08-24 | 2001-09-11 | Rockwell Electronic Commerce Corp. | Method of processing E-mail in an automatic call distributor |
US6198431B1 (en) | 1998-08-27 | 2001-03-06 | Maptrek Llc | Compact GPS tracker and customized mapping system |
US6067045A (en) | 1998-09-01 | 2000-05-23 | Hughes Electronics Corporation | Communication network initialization apparatus and method for fast GPS-based positioning |
US6327473B1 (en) | 1998-09-08 | 2001-12-04 | Qualcomm Incorporated | Method and apparatus for increasing the sensitivity of a global positioning satellite receiver |
US6665539B2 (en) | 1998-09-09 | 2003-12-16 | Qualcomm Inc. | Position location with low tolerance oscillator |
US6360102B1 (en) | 1998-09-10 | 2002-03-19 | Ericsson Inc. | System and method for defining a subscriber location privacy profile |
US6124810A (en) | 1998-09-15 | 2000-09-26 | Qualcomm Incorporated | Method and apparatus for automatic event detection in a wireless communication system |
DE59914910D1 (en) | 1998-09-18 | 2009-01-08 | Siemens Entpr Communications | Method and arrangement for cordless communication by means of at least two switching computers |
US20070121601A1 (en) | 1998-09-24 | 2007-05-31 | Genesys Telecommunications Laboratories, Inc | Integrating SIP Control Messaging into Existing Communication Center Routing Infrastructure |
US6363254B1 (en) | 1998-09-30 | 2002-03-26 | Global Research Systems, Inc. | System and method for enciphering and communicating vehicle tracking information |
US20010011247A1 (en) | 1998-10-02 | 2001-08-02 | O'flaherty Kenneth W. | Privacy-enabled loyalty card system and method |
US6253203B1 (en) | 1998-10-02 | 2001-06-26 | Ncr Corporation | Privacy-enhanced database |
US6178506B1 (en) | 1998-10-23 | 2001-01-23 | Qualcomm Inc. | Wireless subscription portability |
US6584552B1 (en) | 1998-11-02 | 2003-06-24 | Matsushita Electric Industrial Co., Ltd. | Recording/reproducing apparatus, program recorded medium, recorded medium, cache device, and transmitter |
US6321092B1 (en) | 1998-11-03 | 2001-11-20 | Signal Soft Corporation | Multiple input data management for wireless location-based applications |
US6324524B1 (en) | 1998-11-03 | 2001-11-27 | Nextcard, Inc. | Method and apparatus for an account level offer of credit and real time balance transfer |
US20040198386A1 (en) | 2002-01-16 | 2004-10-07 | Dupray Dennis J. | Applications for a wireless location gateway |
US20020111172A1 (en) | 2001-02-14 | 2002-08-15 | Dewolf Frederik M. | Location based profiling |
US6219557B1 (en) | 1998-12-11 | 2001-04-17 | Ericsson Inc. | System and method for providing location services in parallel to existing services in general packet radio services architecture |
US6223046B1 (en) | 1998-12-15 | 2001-04-24 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method for coordinating notification requests for terminal availability |
US6463272B1 (en) | 1998-12-21 | 2002-10-08 | Intel Corporation | Location reporting pager |
US6330454B1 (en) | 1998-12-31 | 2001-12-11 | Nortel Networks Limited | System and method for locating mobile units operating within a wireless communication system |
DE19901296A1 (en) | 1999-01-15 | 2000-07-27 | Voith Turbo Kg | Hydrodynamic clutch |
US6360093B1 (en) | 1999-02-05 | 2002-03-19 | Qualcomm, Incorporated | Wireless push-to-talk internet broadcast |
US6912230B1 (en) | 1999-02-05 | 2005-06-28 | Tecore | Multi-protocol wireless communication apparatus and method |
US6058338A (en) | 1999-02-12 | 2000-05-02 | Qualcomm Incorporated | Method and apparatus for efficient GPS assistance in a communication system |
US6297768B1 (en) | 1999-02-25 | 2001-10-02 | Lunareye, Inc. | Triggerable remote controller |
SE9900710L (en) | 1999-02-25 | 2000-08-26 | Ericsson Telefon Ab L M | Method and device relating to communication networks for mobile phones |
US6247135B1 (en) | 1999-03-03 | 2001-06-12 | Starfish Software, Inc. | Synchronization process negotiation for computing devices |
US6449476B1 (en) | 1999-03-12 | 2002-09-10 | Qualcomm Incorporated | System and method for independently downloading features into a set of storage locations in a wireless communication device |
DE19912871A1 (en) | 1999-03-22 | 2000-09-28 | Emitec Emissionstechnologie | Method and device for producing a metallic honeycomb body |
US6367019B1 (en) | 1999-03-26 | 2002-04-02 | Liquid Audio, Inc. | Copy security for portable music players |
US7136838B1 (en) | 1999-03-27 | 2006-11-14 | Microsoft Corporation | Digital license and method for obtaining/providing a digital license |
US7103574B1 (en) | 1999-03-27 | 2006-09-05 | Microsoft Corporation | Enforcement architecture and method for digital rights management |
US7024393B1 (en) | 1999-03-27 | 2006-04-04 | Microsoft Corporation | Structural of digital rights management (DRM) system |
US6188354B1 (en) | 1999-03-29 | 2001-02-13 | Qualcomm Incorporated | Method and apparatus for determining the location of a remote station in a CDMA communication network |
US6577271B1 (en) | 1999-03-30 | 2003-06-10 | Sirf Technology, Inc | Signal detector employing coherent integration |
US6411892B1 (en) | 2000-07-13 | 2002-06-25 | Global Locate, Inc. | Method and apparatus for locating mobile receivers using a wide area reference network for propagating ephemeris |
US6453237B1 (en) | 1999-04-23 | 2002-09-17 | Global Locate, Inc. | Method and apparatus for locating and providing services to mobile devices |
US6301545B1 (en) | 1999-04-30 | 2001-10-09 | Sirf Technology, Inc. | Global positioning system tag system |
US6564261B1 (en) | 1999-05-10 | 2003-05-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Distributed system to intelligently establish sessions between anonymous users over various networks |
US6560456B1 (en) | 1999-05-24 | 2003-05-06 | Openwave Systems, Inc. | System and method for providing subscriber-initiated information over the short message service (SMS) or a microbrowser |
US6504491B1 (en) | 1999-05-27 | 2003-01-07 | Motorola, Inc. | Simultaneous multi-data stream transmission method and apparatus |
US6621810B1 (en) | 1999-05-27 | 2003-09-16 | Cisco Technology, Inc. | Mobile IP intra-agent mobility |
SE9902462L (en) | 1999-06-28 | 2000-11-06 | Ericsson Telefon Ab L M | Method and device in a telecommunication system |
DE69927144T2 (en) | 1999-07-13 | 2006-06-08 | Motorola, Inc., Schaumburg | Provision of information services in a telecommunications network |
US6539200B1 (en) | 1999-07-29 | 2003-03-25 | Qualcomm, Incorporated | Method and apparatus for paging a user terminal within the “sweet spot” of a satellite |
US6321091B1 (en) | 1999-07-29 | 2001-11-20 | Bryan Holland | Portable locator system and method |
US6549776B1 (en) | 1999-07-30 | 2003-04-15 | Telefonaktiebolaget Lm Ericsson (Publ) | System, method, and apparatus for pushing data in a direct digital call environment |
US6529500B1 (en) | 1999-08-26 | 2003-03-04 | Verizon Laboratories Inc. | Unified messaging notification |
US6542743B1 (en) | 1999-08-31 | 2003-04-01 | Qualcomm, Incorporated | Method and apparatus for reducing pilot search times utilizing mobile station location information |
DE60035649T2 (en) | 1999-09-06 | 2007-11-22 | Honda Giken Kogyo K.K. | Motorcycle with navigation system |
US6775255B1 (en) | 1999-09-16 | 2004-08-10 | At&T Corp. | H.323 mobility architecture for terminal, user and service mobility |
DE19945124A1 (en) | 1999-09-21 | 2001-04-26 | Mannesmann Vdo Ag | Vehicle in-car navigation method involves setting actual position back to control position if spacing between positions exceed error value such that error value is changed depending on reliability test |
US6829475B1 (en) | 1999-09-22 | 2004-12-07 | Motorola, Inc. | Method and apparatus for saving enhanced information contained in content sent to a wireless communication device |
US6392592B1 (en) | 1999-09-30 | 2002-05-21 | Siemens Automotive Corporation | Hand held car locator |
US6865171B1 (en) | 1999-10-22 | 2005-03-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and apparatus for selectively providing user-specific information to origin servers in wireless application protocol applications |
US6795444B1 (en) | 1999-10-26 | 2004-09-21 | Telefonaktiebolaget L M Ericsson (Publ) | System and method for providing wireless telephony over a packet-switched network |
US6816719B1 (en) | 1999-11-03 | 2004-11-09 | Nokia Corporation | Method and system for making wireless terminal profile information accessible to a network |
EP1109374A3 (en) | 1999-12-13 | 2001-06-27 | TELEFONAKTIEBOLAGET LM ERICSSON (publ) | Method and apparatus for performing network operations |
US7603411B1 (en) | 1999-12-14 | 2009-10-13 | Nortel Networks Limited | Presence management system |
US6526322B1 (en) | 1999-12-16 | 2003-02-25 | Sirf Technology, Inc. | Shared memory architecture in GPS signal processing |
US7047411B1 (en) | 1999-12-17 | 2006-05-16 | Microsoft Corporation | Server for an electronic distribution system and method of operating same |
US6996720B1 (en) | 1999-12-17 | 2006-02-07 | Microsoft Corporation | System and method for accessing protected content in a rights-management architecture |
IT1311270B1 (en) | 1999-12-22 | 2002-03-12 | Bitron Spa | PRESSURE DETECTOR DEVICE, PARTICULARLY FOR AN AIR CONDITIONING SYSTEM. |
US6775267B1 (en) | 1999-12-30 | 2004-08-10 | At&T Corp | Method for billing IP broadband subscribers |
US6571095B1 (en) | 1999-12-30 | 2003-05-27 | Nokia Internet Communications Inc. | System and method for providing address discovery of services in mobile networks |
US6687360B2 (en) | 1999-12-30 | 2004-02-03 | At&T Corp. | Personal IP follow-me service |
US6940826B1 (en) | 1999-12-30 | 2005-09-06 | Nortel Networks Limited | Apparatus and method for packet-based media communications |
AU2629601A (en) | 2000-01-07 | 2001-07-24 | Informio, Inc. | Methods and apparatus for an audio web retrieval telephone system |
US6772340B1 (en) | 2000-01-14 | 2004-08-03 | Microsoft Corporation | Digital rights management system operating on computing device and having black box tied to computing device |
US6556832B1 (en) | 2000-02-04 | 2003-04-29 | Qualcomm Incorporated | Method and apparatus for evaluation of position location performance |
US6876734B1 (en) | 2000-02-29 | 2005-04-05 | Emeeting.Net, Inc. | Internet-enabled conferencing system and method accommodating PSTN and IP traffic |
EP2271170B1 (en) | 2000-03-03 | 2012-09-05 | Qualcomm Incorporated | Method and apparatus for participating in group communication services in an existing communication system |
US6477150B1 (en) | 2000-03-03 | 2002-11-05 | Qualcomm, Inc. | System and method for providing group communication services in an existing communication system |
BR0108899A (en) | 2000-03-03 | 2005-10-18 | Qualcomm Inc | Method and apparatus for participating in group communication services in an existing communication system |
US6714793B1 (en) | 2000-03-06 | 2004-03-30 | America Online, Inc. | Method and system for instant messaging across cellular networks and a public data network |
US6434381B1 (en) | 2000-03-08 | 2002-08-13 | Motorola, Inc. | Method and apparatus in a wireless communication system for retrieving local information and services |
US6720915B2 (en) | 2000-03-20 | 2004-04-13 | Snaptrack Incorporated | Methods and apparatuses for using assistance data relating to satellite position systems |
EP1146701B1 (en) | 2000-03-24 | 2005-11-09 | AllisBlue s.a. | Method of transferring data being stored in a database |
US6553236B1 (en) | 2000-03-28 | 2003-04-22 | Ericsson Inc. | On demand location function for mobile terminal |
US6542734B1 (en) | 2000-03-30 | 2003-04-01 | Qualcomm Incorporated | Method and apparatus for detecting specified events in a mobile station |
KR100449468B1 (en) | 2000-03-31 | 2004-09-18 | 가부시키가이샤 엔.티.티.도코모 | Position information informing method and mobile communication terminal |
US7110773B1 (en) | 2000-04-11 | 2006-09-19 | Telecommunication Systems, Inc. | Mobile activity status tracker |
US20070136592A1 (en) | 2000-04-12 | 2007-06-14 | Smith Richard A | Wireless internet gateway |
GB2361389B (en) | 2000-04-15 | 2004-01-28 | Ericsson Telefon Ab L M | Telecommunications system |
US6728701B1 (en) | 2000-04-18 | 2004-04-27 | Claritech Corporation | Method and apparatus for database retrieval utilizing vector optimization |
US6891811B1 (en) | 2000-04-18 | 2005-05-10 | Telecommunication Systems Inc. | Short messaging service center mobile-originated to HTTP internet communications |
US6731940B1 (en) | 2000-04-28 | 2004-05-04 | Trafficmaster Usa, Inc. | Methods of using wireless geolocation to customize content and delivery of information to wireless communication devices |
US6665541B1 (en) | 2000-05-04 | 2003-12-16 | Snaptrack, Incorporated | Methods and apparatuses for using mobile GPS receivers to synchronize basestations in cellular networks |
US6737989B2 (en) | 2000-05-17 | 2004-05-18 | Omega Patents, L.L.C. | Vehicle tracker including variable frequency transmission and related methods |
US6778136B2 (en) | 2001-12-13 | 2004-08-17 | Sirf Technology, Inc. | Fast acquisition of GPS signal |
US6389291B1 (en) | 2000-08-14 | 2002-05-14 | Sirf Technology | Multi-mode global positioning system for use with wireless networks |
US6671620B1 (en) | 2000-05-18 | 2003-12-30 | Sirf Technology, Inc. | Method and apparatus for determining global position using almanac information |
US6427120B1 (en) | 2000-08-14 | 2002-07-30 | Sirf Technology, Inc. | Information transfer in a multi-mode global positioning system used with wireless networks |
US6538757B1 (en) | 2000-05-19 | 2003-03-25 | Pitney Bowes Inc. | Method for automatically reading electronic tickets |
CN100559795C (en) | 2000-05-29 | 2009-11-11 | 诺基亚有限公司 | Method for synchronous |
US6539232B2 (en) | 2000-06-10 | 2003-03-25 | Telcontar | Method and system for connecting mobile users based on degree of separation |
US6505049B1 (en) | 2000-06-23 | 2003-01-07 | Motorola, Inc. | Method and apparatus in a communication network for facilitating a use of location-based applications |
US6795699B1 (en) | 2000-06-27 | 2004-09-21 | Motorola, Inc. | Geolocation techniques for an airborne cellular system |
US6895249B2 (en) | 2000-07-14 | 2005-05-17 | Qualcomm Incorporated | Method and apparatus for broadcasting position location data in a wireless communication system |
US7024321B1 (en) | 2000-07-20 | 2006-04-04 | Qualcomm, Incorporated | Battery monitoring system with low power and end-of-life messaging and shutdown |
US6757828B1 (en) | 2000-07-27 | 2004-06-29 | Jonathan E. Jaffe | Indigenous authentication for sensor-recorders and other information capture devices |
US6687504B1 (en) | 2000-07-28 | 2004-02-03 | Telefonaktiebolaget L. M. Ericsson | Method and apparatus for releasing location information of a mobile communications device |
US6775802B2 (en) | 2000-08-08 | 2004-08-10 | Qualcomm Incorporated | Method, apparatus, and system for signal prediction |
US6529829B2 (en) | 2000-08-24 | 2003-03-04 | Sirf Technology, Inc. | Dead reckoning system for reducing auto-correlation or cross-correlation in weak signals |
US6938019B1 (en) | 2000-08-29 | 2005-08-30 | Uzo Chijioke Chukwuemeka | Method and apparatus for making secure electronic payments |
US6665612B1 (en) | 2000-08-29 | 2003-12-16 | Sirf Technology, Inc. | Navigation processing for a satellite positioning system receiver |
NL1017189C1 (en) | 2000-08-30 | 2002-03-01 | Koninkl Kpn Nv | Method and system for activation of a local terminal. |
FI20001918A (en) | 2000-08-30 | 2002-03-01 | Nokia Corp | Multimodal content automatic voice identification in a wireless telecommunication system |
US6618593B1 (en) | 2000-09-08 | 2003-09-09 | Rovingradar, Inc. | Location dependent user matching system |
US6351711B1 (en) | 2000-09-14 | 2002-02-26 | Sirf Technology, Inc. | GPS navigation system using neural networks |
US6618670B1 (en) | 2000-09-15 | 2003-09-09 | Sirf Technology, Inc. | Resolving time ambiguity in GPS using over-determined navigation solution |
US6609004B1 (en) | 2000-09-22 | 2003-08-19 | Motorola Inc | Communication management system for personalized mobility management of wireless services and method therefor |
US6810323B1 (en) | 2000-09-25 | 2004-10-26 | Motorola, Inc. | System and method for storing and using information associated with geographic locations of interest to a mobile user |
US6748195B1 (en) | 2000-09-29 | 2004-06-08 | Motorola, Inc. | Wireless device having context-based operational behavior |
US6771971B2 (en) | 2000-10-10 | 2004-08-03 | Sws Development, L.L.C. | Subscriber information service center (SISC) |
US6697629B1 (en) | 2000-10-11 | 2004-02-24 | Qualcomm, Incorporated | Method and apparatus for measuring timing of signals received from multiple base stations in a CDMA communication system |
US6778885B2 (en) | 2000-10-16 | 2004-08-17 | Qualcomm Inc. | Apparatus, method, and system of transferring correction information |
US6718174B2 (en) | 2000-10-27 | 2004-04-06 | Qualcomm Incorporated | Method and apparatus for estimating velocity of a terminal in a wireless communication system |
US6640184B1 (en) | 2000-11-10 | 2003-10-28 | Motorola, Inc. | Method and apparatus for providing location information |
US6937187B2 (en) | 2000-11-17 | 2005-08-30 | Global Locate, Inc. | Method and apparatus for forming a dynamic model to locate position of a satellite receiver |
US6560534B2 (en) | 2001-06-06 | 2003-05-06 | Global Locate, Inc. | Method and apparatus for distributing satellite tracking information |
US6832373B2 (en) | 2000-11-17 | 2004-12-14 | Bitfone Corporation | System and method for updating and distributing information |
US6417801B1 (en) | 2000-11-17 | 2002-07-09 | Global Locate, Inc. | Method and apparatus for time-free processing of GPS signals |
US6804524B1 (en) | 2000-11-21 | 2004-10-12 | Openwave Systems Inc. | System and method for the acquisition of automobile traffic data through wireless networks |
US6970917B1 (en) | 2000-12-05 | 2005-11-29 | Mformation Technologies Inc. | System and method for remote control and management of wireless devices |
US20020112047A1 (en) | 2000-12-05 | 2002-08-15 | Rakesh Kushwaha | System and method for wireless data terminal management using general packet radio service network |
US6377793B1 (en) | 2000-12-06 | 2002-04-23 | Xybernaut Corporation | System and method of accessing and recording messages at coordinate way points |
US7110749B2 (en) | 2000-12-19 | 2006-09-19 | Bellsouth Intellectual Property Corporation | Identity blocking service from a wireless service provider |
US20020077897A1 (en) | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Identity blocking service from a web advertiser |
US7224978B2 (en) | 2000-12-19 | 2007-05-29 | Bellsouth Intellectual Property Corporation | Location blocking service from a wireless service provider |
US7085555B2 (en) | 2000-12-19 | 2006-08-01 | Bellsouth Intellectual Property Corporation | Location blocking service from a web advertiser |
US6799049B1 (en) | 2000-12-19 | 2004-09-28 | Bellsouth Intellectual Property Corporation | System and method for tracking movement of a wireless device |
FI112902B (en) | 2000-12-28 | 2004-01-30 | Nokia Corp | A method for transmitting a location-dependent message, a messaging system, and a wireless communication device |
US20020098832A1 (en) | 2001-01-22 | 2002-07-25 | Wolfgang Fleischer | Intelligent personalized customer service |
US6744858B1 (en) | 2001-01-26 | 2004-06-01 | Telcontrol, Inc. | System and method for supporting multiple call centers |
US6744856B2 (en) | 2001-01-31 | 2004-06-01 | Lucent Technologies Inc. | Method and apparatus for servicing emergency calls from a data network |
US6703971B2 (en) | 2001-02-21 | 2004-03-09 | Sirf Technologies, Inc. | Mode determination for mobile GPS terminals |
US7012901B2 (en) | 2001-02-28 | 2006-03-14 | Cisco Systems, Inc. | Devices, software and methods for generating aggregate comfort noise in teleconferencing over VoIP networks |
US6757545B2 (en) | 2001-03-01 | 2004-06-29 | Steven P. Nowak | Location information management system and method for mobile communications unit |
US6701144B2 (en) | 2001-03-05 | 2004-03-02 | Qualcomm Incorporated | System for automatically configuring features on a mobile telephone based on geographic location |
US6570530B2 (en) | 2001-03-05 | 2003-05-27 | Qualcomm Incorporated | Method and apparatus providing improved position estimate based on an initial coarse position estimate |
KR100369803B1 (en) | 2001-03-10 | 2003-02-05 | 삼성전자 주식회사 | Packet voice call service method in wireless telecommunication network and network architecture therefor |
KR100898530B1 (en) | 2001-03-15 | 2009-05-20 | 퀄컴 인코포레이티드 | Time acquisition in a wireless position determination system |
US7065507B2 (en) | 2001-03-26 | 2006-06-20 | Microsoft Corporation | Supervised license acquisition in a digital rights management system on a computing device |
US6895238B2 (en) | 2001-03-30 | 2005-05-17 | Motorola, Inc. | Method for providing entertainment to a portable device |
US6867733B2 (en) | 2001-04-09 | 2005-03-15 | At Road, Inc. | Method and system for a plurality of mobile units to locate one another |
FI112314B (en) | 2001-04-11 | 2003-11-14 | Sonera Oyj | Procedure and system for using the information on the status of terminal equipment |
EP1263187B1 (en) | 2001-04-23 | 2013-07-31 | Koninklijke KPN N.V. | Service provider architecture and method for delivering content services to mobile communication customers |
US6745038B2 (en) | 2001-04-30 | 2004-06-01 | Motorola, Inc. | Intra-piconet location determination and tomography |
US7489918B2 (en) | 2003-05-09 | 2009-02-10 | Intel Corporation | System and method for transferring wireless network access passwords |
ATE293871T1 (en) | 2001-05-11 | 2005-05-15 | Nokia Corp | MOBILE INSTANT MESSAGING AND PRESENCE SERVICE |
US6594483B2 (en) | 2001-05-15 | 2003-07-15 | Nokia Corporation | System and method for location based web services |
US7472396B2 (en) | 2001-05-18 | 2008-12-30 | Qualcomm Incorporated | Extensible event notification mechanism |
US7464178B2 (en) | 2001-05-23 | 2008-12-09 | Markport Limited | Open messaging gateway |
US6799050B1 (en) | 2001-06-04 | 2004-09-28 | Snaptrack, Inc. | Reducing cross-interference in a combined GPS receiver and communication system |
US6427001B1 (en) | 2001-06-07 | 2002-07-30 | Bellsouth Intellectual Property Corporation | System and method for notification of 911 telephone calls using a link monitoring system |
US6912545B1 (en) | 2001-06-12 | 2005-06-28 | Sprint Spectrum L.P. | Location-code system for location-based services |
US6954442B2 (en) | 2001-06-14 | 2005-10-11 | Flarion Technologies, Inc. | Methods and apparatus for using a paging and location server to support session signaling |
US20020191595A1 (en) | 2001-06-18 | 2002-12-19 | Mar Jack K. | Providing communications capabilities to mobile devices at an enterprise |
US7161939B2 (en) | 2001-06-29 | 2007-01-09 | Ip Unity | Method and system for switching among independent packetized audio streams |
US6515623B2 (en) | 2001-06-29 | 2003-02-04 | Motorola, Inc. | Enhanced location methodology for a location system |
US6594576B2 (en) | 2001-07-03 | 2003-07-15 | At Road, Inc. | Using location data to determine traffic information |
US7075900B2 (en) | 2001-07-10 | 2006-07-11 | D.B. Zwirn Finance, Llc | Software based single agent multipoint conference capability |
US20030013449A1 (en) | 2001-07-11 | 2003-01-16 | Hose David A. | Monitoring boundary crossings in a wireless network |
AU2002354975A1 (en) | 2001-07-16 | 2003-03-03 | Wavemarket Inc. | System for providing alert-based services to mobile stations in a wireless communications network |
US7333820B2 (en) | 2001-07-17 | 2008-02-19 | Networks In Motion, Inc. | System and method for providing routing, mapping, and relative position information to users of a communication network |
US7023465B2 (en) | 2001-07-31 | 2006-04-04 | Tandberg Telecom As | System and method for communication device configuration, scheduling and access control |
US6996087B2 (en) | 2001-07-31 | 2006-02-07 | Lucent Technologies Inc. | Communication system including an interworking mobile switching center for call termination |
JP4236398B2 (en) | 2001-08-15 | 2009-03-11 | 富士通株式会社 | Communication method, communication system, and communication connection program |
US6757544B2 (en) | 2001-08-15 | 2004-06-29 | Motorola, Inc. | System and method for determining a location relevant to a communication device and/or its associated user |
US20030040272A1 (en) | 2001-08-24 | 2003-02-27 | Charles Lelievre | Location-based selection of radio content sources |
EP1433066B1 (en) | 2001-09-14 | 2010-08-11 | Nokia Inc. | Device and method for packet forwarding |
US6941144B2 (en) | 2001-09-14 | 2005-09-06 | Qualcomm Incorporated | Method and apparatus for detecting excess delay in a communication signal |
US7082313B2 (en) | 2001-09-24 | 2006-07-25 | Qualcomm Incorporated | Secure short message service |
US6912395B2 (en) | 2001-09-25 | 2005-06-28 | Motorola, Inc. | Network and method for monitoring location capabilities of a mobile station |
US6606554B2 (en) | 2001-09-27 | 2003-08-12 | Siemens Information & Communication Mobile Llc | Method and apparatus for defining location coordinates |
US7570668B2 (en) | 2001-10-03 | 2009-08-04 | Nokia Corporation | Data synchronization |
US7155521B2 (en) | 2001-10-09 | 2006-12-26 | Nokia Corporation | Starting a session in a synchronization system |
US6965754B2 (en) | 2001-10-09 | 2005-11-15 | Motorola, Inc. | Satellite positioning system receiver with reference oscillator circuit and methods therefor |
US6900758B1 (en) | 2001-10-17 | 2005-05-31 | Sirf Technology, Inc. | System, method, apparatus and means for constructing building tomography and timing information |
US6950058B1 (en) | 2001-10-17 | 2005-09-27 | Sirf Technology, Inc. | System, method, apparatus and means for providing GPS aiding data to networked receivers |
ES2305114T3 (en) | 2001-10-17 | 2008-11-01 | Spyder Navigations L.L.C. | PROCEDURE TO INFORM A NETWORK OF THE AMOUNT OF DATA TO TRANSFER. |
US6816580B2 (en) | 2001-10-19 | 2004-11-09 | Metro One Telecommunications, Inc. | Technique for attributing communication call transactions to user affiliations and adjusting billings thereof |
US20030078064A1 (en) | 2001-10-22 | 2003-04-24 | Chan Victor H. | System and method for queuing talk requests in wireless dispatch system |
US20030100320A1 (en) | 2001-10-31 | 2003-05-29 | Peeyush Ranjan | Efficient hyperlinks for transmitted hyperlinked information |
US6813264B2 (en) | 2001-11-02 | 2004-11-02 | Qualcomm, Incorporated | System and method for routing voice over IP calls |
US7133365B2 (en) | 2001-11-02 | 2006-11-07 | Internap Network Services Corporation | System and method to provide routing control of information over networks |
US20030109245A1 (en) | 2001-11-05 | 2003-06-12 | Mccalmont Patti L | Routing of emergency calls based on geographic location of originating telephone end office |
US6771742B2 (en) | 2001-11-05 | 2004-08-03 | Intrado Inc. | Geographic routing of emergency service call center emergency calls |
US6756938B2 (en) | 2001-11-06 | 2004-06-29 | Motorola, Inc. | Satellite positioning system receivers and methods therefor |
EP1315389A1 (en) | 2001-11-16 | 2003-05-28 | Telefonaktiebolaget Lm Ericsson | Method for the determination of a receiver for location information |
US20030101341A1 (en) | 2001-11-26 | 2003-05-29 | Electronic Data Systems Corporation | Method and system for protecting data from unauthorized disclosure |
US6885874B2 (en) | 2001-11-27 | 2005-04-26 | Motorola, Inc. | Group location and route sharing system for communication units in a trunked communication system |
US6882850B2 (en) | 2001-12-03 | 2005-04-19 | Sprint Spectrum L.P. | Method and system for zone-based capacity control |
KR100691537B1 (en) | 2001-12-03 | 2007-03-09 | 노키아 코포레이션 | Apparatus, and associated method, for retrieving mobile-node logic tree information |
US7610390B2 (en) | 2001-12-04 | 2009-10-27 | Sun Microsystems, Inc. | Distributed network identity |
US7162221B2 (en) | 2001-12-14 | 2007-01-09 | Inphonic, Inc. | Systems, methods, and computer program products for registering wireless device users in direct marketing campaigns |
US6691019B2 (en) | 2001-12-21 | 2004-02-10 | General Electric Company | Method and system for controlling distortion of turbine case due to thermal variations |
US7853272B2 (en) | 2001-12-21 | 2010-12-14 | Telecommunication Systems, Inc. | Wireless network tour guide |
US20030119528A1 (en) | 2001-12-26 | 2003-06-26 | Boathouse Communication Partners, Llc | System and method for an automated intermediary to broker remote transaction between parties based on actively managed private profile information |
US7072667B2 (en) | 2001-12-31 | 2006-07-04 | Nokia Corporation | Location information service for a cellular telecommunications network |
US6947772B2 (en) | 2002-01-31 | 2005-09-20 | Qualcomm Incorporated | System and method for providing messages on a wireless device connecting to an application server |
US6721578B2 (en) | 2002-01-31 | 2004-04-13 | Qualcomm Incorporated | System and method for providing an interactive screen on a wireless device interacting with a server |
KR100711913B1 (en) | 2002-02-04 | 2007-04-27 | 엘지전자 주식회사 | Method for securing data stored in hard discs of a computer system |
US6856282B2 (en) | 2002-02-08 | 2005-02-15 | Qualcomm Incorporated | Directly acquiring precision code GPS signals |
US6873854B2 (en) | 2002-02-14 | 2005-03-29 | Qualcomm Inc. | Method and an apparatus for adding a new member to an active group call in a group communication network |
US6781963B2 (en) | 2002-02-14 | 2004-08-24 | Qualcomm Inc | Method and an apparatus for terminating a user from a group call in a group communication network |
US20030153341A1 (en) | 2002-02-14 | 2003-08-14 | Crockett Douglas M. | Server for initiating a group call in a group communication network |
US20030153340A1 (en) | 2002-02-14 | 2003-08-14 | Crockett Douglas M. | Server for joining a user to a group call in a group communication network |
US20030153343A1 (en) | 2002-02-14 | 2003-08-14 | Crockett Douglas M. | Communication device for initiating a group call in a group communication network |
US6898436B2 (en) | 2002-02-14 | 2005-05-24 | Qualcomm Incorporated | Communication device for joining a user to a group call in a group communication network |
US6993355B1 (en) | 2002-02-22 | 2006-01-31 | Verizon Services Corp. | Methods and apparatus for connecting family members |
US8397060B2 (en) | 2002-02-22 | 2013-03-12 | Nokia Corporation | Requesting digital certificates |
US6801159B2 (en) | 2002-03-19 | 2004-10-05 | Motorola, Inc. | Device for use with a portable inertial navigation system (“PINS”) and method for transitioning between location technologies |
US7426380B2 (en) | 2002-03-28 | 2008-09-16 | Telecommunication Systems, Inc. | Location derived presence information |
US7200380B2 (en) | 2002-03-28 | 2007-04-03 | Telecommunication Systems, Inc. | Wireless telecommunications location based services scheme selection |
US6944540B2 (en) | 2002-03-28 | 2005-09-13 | Motorola, Inc. | Time determination in satellite positioning system receivers and methods therefor |
US7321773B2 (en) | 2002-03-28 | 2008-01-22 | Telecommunication Systems, Inc. | Area watcher for wireless network |
US6721871B2 (en) | 2002-04-02 | 2004-04-13 | Nokia Corporation | Method and apparatus for synchronizing data stores with respect to changes in folders |
JP4199475B2 (en) | 2002-04-11 | 2008-12-17 | 日本電気株式会社 | Positioning gateway device, terminal location information request processing method and program |
US20030196105A1 (en) | 2002-04-12 | 2003-10-16 | Victoria Fineberg | Remote access VPN extranets |
US6937872B2 (en) | 2002-04-15 | 2005-08-30 | Qualcomm Incorporated | Methods and apparatuses for measuring frequencies of basestations in cellular networks using mobile GPS receivers |
US6724342B2 (en) | 2002-04-19 | 2004-04-20 | Sirf Technology, Inc. | Compensation for frequency adjustment in mobile communication-positioning device with shared oscillator |
US6973320B2 (en) | 2002-04-29 | 2005-12-06 | Motorola, Inc. | Method and apparatus for locating a remote unit within a communication system |
CA2482688C (en) | 2002-04-30 | 2013-06-18 | Nokia Corporation | Method and device for management of tree data exchange |
JP4340626B2 (en) | 2002-05-13 | 2009-10-07 | トムソン ライセンシング | Seamless public wireless local area network user authentication |
WO2003098258A1 (en) | 2002-05-17 | 2003-11-27 | Motorola, Inc., A Corporation Of The State Of Delaware | Frequency management in a communications positioning device |
US6650288B1 (en) | 2002-05-23 | 2003-11-18 | Telecommunication Systems | Culled satellite ephemeris information for quick assisted GPS location determination |
US6580390B1 (en) | 2002-05-30 | 2003-06-17 | General Motors Corporation | Method and system for global positioning system mask angle optimization |
US7136466B1 (en) | 2002-05-30 | 2006-11-14 | Bellsouth Intellectual Property Corporation | DSL integrated call waiting |
US8576878B2 (en) | 2002-06-04 | 2013-11-05 | Nokia Corporation | Method for controlling parties in real-time data communication |
US6961562B2 (en) | 2002-06-19 | 2005-11-01 | Openwave Systems Inc. | Method and apparatus for acquiring, processing, using and brokering location information associated with mobile communication devices |
US6738013B2 (en) | 2002-06-20 | 2004-05-18 | Sirf Technology, Inc. | Generic satellite positioning system receivers with selective inputs and outputs |
US6747596B2 (en) | 2002-06-20 | 2004-06-08 | Sirf Technology, Inc. | Generic satellite positioning system receivers with programmable inputs |
US7502610B2 (en) | 2002-06-28 | 2009-03-10 | Qualcomm Incorporated | System and method for application management through threshold events |
JP4016787B2 (en) | 2002-07-31 | 2007-12-05 | 日本電気株式会社 | Positioning system in mobile communication network |
GB0218028D0 (en) | 2002-08-02 | 2002-09-11 | Nokia Corp | Location services for mobile communication system |
US7813484B2 (en) | 2002-08-08 | 2010-10-12 | Telecommunication Systems, Inc. | All-HTTP multimedia messaging |
US6865395B2 (en) | 2002-08-08 | 2005-03-08 | Qualcomm Inc. | Area based position determination for terminals in a wireless network |
AU2003257054A1 (en) | 2002-08-16 | 2004-03-03 | Nuasis Corporation | Escalated handling of non-realtime communications |
US20040044623A1 (en) | 2002-08-28 | 2004-03-04 | Wake Susan L. | Billing system for wireless device activity |
US8032149B2 (en) | 2002-08-29 | 2011-10-04 | Andrew Llc | Tasking and reporting method and implementation for wireless appliance location systems |
US6907238B2 (en) | 2002-08-30 | 2005-06-14 | Qualcomm Incorporated | Beacon for locating and tracking wireless terminals |
US20040068724A1 (en) | 2002-08-30 | 2004-04-08 | Gardner Richard Wayne | Server processing for updating dataset versions resident on a wireless device |
US6839417B2 (en) | 2002-09-10 | 2005-01-04 | Myriad Entertainment, Inc. | Method and apparatus for improved conference call management |
US7212806B2 (en) | 2002-09-12 | 2007-05-01 | Broadcom Corporation | Location-based transaction authentication of wireless terminal |
US6816734B2 (en) | 2002-09-17 | 2004-11-09 | Motorola, Inc. | Method and apparatus for improved location determination in a private radio network using a public network system |
US6957073B2 (en) | 2002-09-18 | 2005-10-18 | Motorola, Inc. | Mobile location explorer and methods therefor |
US6741842B2 (en) | 2002-09-30 | 2004-05-25 | Motorola, Inc. | System and method for frequency management in a communication device having a positioning device |
AU2003284292A1 (en) | 2002-10-21 | 2004-05-13 | Bitfone Corporation | System with required enhancements to syncml dm environment to support firmware updates |
US6903684B1 (en) | 2002-10-22 | 2005-06-07 | Qualcomm Incorporated | Method and apparatus for optimizing GPS-based position location in presence of time varying frequency error |
US7302254B2 (en) | 2002-11-08 | 2007-11-27 | Openwave Systems Inc. | MMS based photo album publishing system |
EP1559291B1 (en) | 2002-11-08 | 2012-08-01 | Nokia Corporation | Handling location services independently from the cellular communication system |
ATE349862T1 (en) | 2002-11-20 | 2007-01-15 | Cit Alcatel | ACCESS SERVER FOR WEB SERVICES |
AU2002347485A1 (en) | 2002-11-25 | 2004-06-18 | Nokia Corporation | Method and system for session management wherein a client session identifier is used |
US6980816B2 (en) | 2002-11-26 | 2005-12-27 | Motorola, Inc. | Contextual information management in wireless communications devices and methods therefor |
US20040198332A1 (en) | 2002-11-27 | 2004-10-07 | Lundsgaard Soren K. | System and method of automatically answering calls in a wireless communication device |
US6816111B2 (en) | 2002-12-13 | 2004-11-09 | Qualcomm Incorporated | Calibration and correction system for satellite position location systems |
US20040205151A1 (en) | 2002-12-19 | 2004-10-14 | Sprigg Stephen A. | Triggering event processing |
US6888497B2 (en) | 2002-12-27 | 2005-05-03 | Motorola, Inc. | Method and mobile station for determining a code phase |
US6904029B2 (en) | 2003-01-23 | 2005-06-07 | Motorola, Inc. | Method and apparatus for a source-initiated handoff from a source cellular wireless network to a target non-cellular wireless network |
US7065351B2 (en) | 2003-01-30 | 2006-06-20 | Qualcomm Incorporated | Event-triggered data collection |
US6985747B2 (en) | 2003-02-05 | 2006-01-10 | Autodesk, Inc. | Use of triggers and a location hypercube to enable push-based location applications |
US6999782B2 (en) | 2003-02-19 | 2006-02-14 | Motorola, Inc. | Method for joining dispatch calls |
US8023958B2 (en) | 2003-03-05 | 2011-09-20 | Qualcomm Incorporated | User plane-based location services (LCS) system, method and apparatus |
JP4517578B2 (en) | 2003-03-11 | 2010-08-04 | 株式会社日立製作所 | Peer-to-peer communication apparatus and communication method |
US7231218B2 (en) | 2003-03-18 | 2007-06-12 | Openwave Systems Inc. | Lawful intercept service |
US7742620B2 (en) | 2003-03-21 | 2010-06-22 | Lockhead Martin Corporation | Target detection improvements using temporal integrations and spatial fusion |
US7730014B2 (en) | 2003-03-25 | 2010-06-01 | Hartenstein Mark A | Systems and methods for managing affiliations |
US6963557B2 (en) | 2003-03-29 | 2005-11-08 | Intrado Inc. | System and method for routing telephone calls involving internet protocol network |
US7409428B1 (en) | 2003-04-22 | 2008-08-05 | Cooper Technologies Company | Systems and methods for messaging to multiple gateways |
US7930214B2 (en) * | 2003-05-05 | 2011-04-19 | Intel Corporation | Management and arbitration of mobile service discovery |
US7489938B2 (en) | 2003-05-14 | 2009-02-10 | Nokia Corporation | Apparatus and method for providing location information |
US20040235493A1 (en) | 2003-05-23 | 2004-11-25 | Thomas Ekerborn | Tags for location-based services in wireless networks |
US6839020B2 (en) | 2003-06-02 | 2005-01-04 | Motorola, Inc. | Aiding location determinations in satellite positioning system receivers |
US7450566B2 (en) | 2003-06-05 | 2008-11-11 | Oracle International Corporation | Apparatus and method for providing a unified telephony solution |
US6975266B2 (en) | 2003-06-17 | 2005-12-13 | Global Locate, Inc. | Method and apparatus for locating position of a satellite signal receiver |
EP1645154B1 (en) | 2003-06-27 | 2010-03-17 | Nortel Networks Limited | Call routing and corresponding updating of routing information |
EP1639435A4 (en) | 2003-06-27 | 2009-12-30 | Hewlett Packard Development Co | System and method for downloading update packages into a mobile handset in a carrier network |
US6842715B1 (en) | 2003-07-21 | 2005-01-11 | Qualcomm Incorporated | Multiple measurements per position fix improvements |
US6788249B1 (en) | 2003-07-23 | 2004-09-07 | Snaptrack Incorporated | System for setting coarse GPS time in a mobile station within an asynchronous wireless network |
US20050028034A1 (en) | 2003-07-28 | 2005-02-03 | Alexander Gantman | Fault diagnosis, repair and upgrades using the acoustic channel |
GB0319360D0 (en) | 2003-08-18 | 2003-09-17 | Nokia Corp | Setting up communication sessions |
US20050112030A1 (en) | 2003-08-21 | 2005-05-26 | Gaus Stephanie E. | Meshwell plates |
JP4330628B2 (en) | 2003-08-22 | 2009-09-16 | ノキア コーポレイション | Apparatus and associated method for facilitating mobile station location determination according to location-based applications |
US7251312B2 (en) | 2003-09-06 | 2007-07-31 | Intrado Inc. | Method and system for availing participants in a special number call event and others of information contained in a plurality of data stores |
US7330112B1 (en) | 2003-09-09 | 2008-02-12 | Emigh Aaron T | Location-aware services |
US20070019614A1 (en) | 2003-09-09 | 2007-01-25 | Klaus Hoffmann | Method for providing a user interaction dialogue (uid) prior to connection acceptance by the called user |
US8069082B2 (en) | 2003-10-06 | 2011-11-29 | Utbk, Inc. | Methods and apparatuses to determine prices of communication leads |
US7440442B2 (en) | 2003-10-21 | 2008-10-21 | 3Com Corporation | IP-based enhanced emergency services using intelligent client devices |
US7072645B2 (en) | 2003-10-23 | 2006-07-04 | General Motors Corporation | In-vehicle automated call routing using an origin identifier |
US7436785B1 (en) | 2003-11-12 | 2008-10-14 | Sprint Spectrum L.P. | Method and system for location based subject matter teleconferencing |
US20050125493A1 (en) | 2003-11-13 | 2005-06-09 | Hemant Chaskar | IP-based mechanism for location service systems, methods, and devices |
US7877275B2 (en) | 2003-11-13 | 2011-01-25 | General Motors Llc | System and method for maintaining and providing personal information in real time |
ES2300536T3 (en) | 2003-12-02 | 2008-06-16 | Alcatel Lucent | DISSEMINATION OF SERVICES BASED ON THE LOCATION OF A MOBILE TERMINAL IN A WIRELESS NETWORK. |
US6968044B2 (en) | 2003-12-05 | 2005-11-22 | Bellsouth Intellectual Property Corporation | Telephone emergency response system and method |
US7260186B2 (en) | 2004-03-23 | 2007-08-21 | Telecommunication Systems, Inc. | Solutions for voice over internet protocol (VoIP) 911 location services |
US6940950B2 (en) | 2003-12-19 | 2005-09-06 | Telecommunication Systems, Inc. | Enhanced E911 location information using voice over internet protocol (VoIP) |
US20050134504A1 (en) | 2003-12-22 | 2005-06-23 | Lear Corporation | Vehicle appliance having hands-free telephone, global positioning system, and satellite communications modules combined in a common architecture for providing complete telematics functions |
US7937066B2 (en) | 2003-12-22 | 2011-05-03 | 911Tracker, Inc. | Emergency conference calling system |
US7523314B2 (en) | 2003-12-22 | 2009-04-21 | Voltage Security, Inc. | Identity-based-encryption message management system |
US7945494B2 (en) | 2003-12-23 | 2011-05-17 | First Data Corporation | Device with GPS to manage risk for financial transactions |
US7174153B2 (en) | 2003-12-23 | 2007-02-06 | Gregory A Ehlers | System and method for providing information to an operator of an emergency response vehicle |
US20050265318A1 (en) | 2004-01-08 | 2005-12-01 | Nokia Corporation | Apparatus, system, and method for rejecting a session establishment request |
FI20040036A0 (en) | 2004-01-13 | 2004-01-13 | Nokia Corp | Providing location information on a visited network |
US7369530B2 (en) | 2004-01-30 | 2008-05-06 | Scott Keagy | Apparatus and method for interfacing packet-based phone services with emergency call centers |
US8219664B2 (en) | 2004-01-30 | 2012-07-10 | Nokia Corporation | Defining nodes in device management system |
US20050169248A1 (en) | 2004-02-04 | 2005-08-04 | Nortel Networks Limited | Method and apparatus for providing in-band location information in an emergency response network |
US7177399B2 (en) | 2004-02-27 | 2007-02-13 | Nortel Network Limited | Determining the geographical location from which an emergency call originates in a packet-based communications network |
US20050232252A1 (en) | 2004-03-01 | 2005-10-20 | Hoover Thomas R | Communication system with distributed intelligence |
US7130385B1 (en) | 2004-03-05 | 2006-10-31 | Avaya Technology Corp. | Advanced port-based E911 strategy for IP telephony |
AU2005218205B2 (en) | 2004-03-10 | 2010-04-08 | Nokia Corporation | Storage of content-location information |
US7177398B2 (en) | 2004-03-13 | 2007-02-13 | Intrado Inc. | Bi-directional messaging for an emergency services network |
US7123693B2 (en) | 2004-03-13 | 2006-10-17 | Intrado Inc. | Method and apparatus for increasing the reliability of an emergency call communication network |
GB0407823D0 (en) | 2004-04-06 | 2004-05-12 | Nokia Corp | A method of communication |
US20050250516A1 (en) | 2004-04-14 | 2005-11-10 | Lg Electronics Inc. | Location information system reflecting user preferences and service providing method thereof |
US6861980B1 (en) | 2004-05-26 | 2005-03-01 | Qualcomm Incorporated | Data messaging efficiency for an assisted wireless position determination system |
US20050266864A1 (en) | 2004-06-01 | 2005-12-01 | Xuming Chen | Non-intrusive network architecture for mass mobile messaging |
US7573825B2 (en) | 2004-06-02 | 2009-08-11 | At&T Intellectual Property I, Lp | Methods, apparatus and computer program products for testing a voice over Internet protocol communication system |
US8265587B2 (en) | 2004-06-17 | 2012-09-11 | West Corporation | System and method for amending instructions for emergency auxiliary services following an emergency services request |
US8903820B2 (en) | 2004-06-23 | 2014-12-02 | Nokia Corporation | Method, system and computer program to enable querying of resources in a certain context by definition of SIP even package |
US7764944B2 (en) | 2004-06-24 | 2010-07-27 | Alcatel-Lucent Usa Inc. | Method of providing a unique call back number for wireless 9-1-1 calls |
US7209758B1 (en) | 2004-06-25 | 2007-04-24 | Sprint Spectrum L.P. | Method and system for sharing and/or centralizing mobile positioning information and geospatial data for roaming mobile subscriber terminals |
GB0414421D0 (en) | 2004-06-28 | 2004-07-28 | Nokia Corp | Authenticating users |
US7650142B2 (en) | 2004-07-08 | 2010-01-19 | Nortel Networks Limited | Method for setting up a conference call |
US8249102B2 (en) | 2004-07-27 | 2012-08-21 | Motorola Solutions, Inc. | Method and apparatus for session layer framing to enable interoperability between packet-switched systems |
US7260384B2 (en) | 2004-07-29 | 2007-08-21 | Sprint Spectrum L.P. | Method and system for dynamic selection of voice mail system |
US7840681B2 (en) | 2004-07-30 | 2010-11-23 | International Business Machines Corporation | Method and apparatus for integrating wearable devices within a SIP infrastructure |
US20060079249A1 (en) | 2004-08-03 | 2006-04-13 | Lg Electronics Inc. | User privacy management apparatus and method in mobile communications system |
US9723087B2 (en) | 2004-08-03 | 2017-08-01 | Lg Electronics Inc. | User privacy management apparatus and method in mobile communications system |
FI20041169A0 (en) | 2004-09-08 | 2004-09-08 | Nokia Corp | Group Services Group Information |
US7413513B2 (en) | 2004-09-10 | 2008-08-19 | Igt | Apparatus and methods for wireless gaming communications |
KR100575802B1 (en) | 2004-09-13 | 2006-05-03 | 엘지전자 주식회사 | Method and system for roaming in location information system |
US7333480B1 (en) | 2004-09-20 | 2008-02-19 | Nortel Networks Limited | Localization of call routing for TDM sets in an IP network |
US20060068753A1 (en) | 2004-09-22 | 2006-03-30 | Jim Karpen | Emergency call handling system |
US7532713B2 (en) | 2004-09-23 | 2009-05-12 | Vapps Llc | System and method for voice over internet protocol audio conferencing |
US7573982B2 (en) | 2004-10-12 | 2009-08-11 | Bellsouth Intellectual Property Corporation | Methods and systems for managing a call session |
GB0424052D0 (en) | 2004-10-29 | 2004-12-01 | Nortel Networks Ltd | Improvements in or relating to internet protocol (IP) location, privacy and presence |
US7900039B2 (en) | 2005-01-17 | 2011-03-01 | Lg Electronics, Inc. | TLS session management method in SUPL-based positioning system |
US20070041513A1 (en) | 2005-02-08 | 2007-02-22 | Gende Michael F | Emergency call identification, location and routing method and system |
US7756253B2 (en) | 2005-02-22 | 2010-07-13 | At&T Intellectual Property Ii, Lp | Methods and systems for providing foreign call back number compatibility for VoIP E9-1-1 calls |
US7545916B2 (en) | 2005-02-28 | 2009-06-09 | At&T Intellectual Property I | Methods of placing emergency calls using data networks |
EP1859552A4 (en) | 2005-03-15 | 2009-07-29 | Mformation Technologies Inc | System and method for monitoring and measuring end-to-end performance using wireless devices |
US8868717B2 (en) | 2005-03-15 | 2014-10-21 | Mformation Software Technologies Llc | System and method for trap management and monitoring on wireless terminals |
US7532890B2 (en) | 2005-04-01 | 2009-05-12 | Rockliffe Systems | Content-based notification and user-transparent pull operation for simulated push transmission of wireless email |
KR100595714B1 (en) | 2005-04-01 | 2006-07-03 | 엘지전자 주식회사 | Supl initial message and method for processing supl using the same in supl based location information system |
US7283816B2 (en) | 2005-04-14 | 2007-10-16 | Qualcomm Incorporated | Apparatus and process for a universal diagnostic monitor module on a wireless device |
US20060258380A1 (en) | 2005-05-16 | 2006-11-16 | Kai Liebowitz | Interactive opt-in-messaging |
US9154907B2 (en) | 2005-06-21 | 2015-10-06 | Qualcomm Incorporated | Efficient periodic location reporting in a radio access network |
US20070003024A1 (en) | 2005-06-22 | 2007-01-04 | Cml Emergency Services Inc. | Network emergency call taking system and method |
US20060293024A1 (en) | 2005-06-23 | 2006-12-28 | Lucent Technologies Inc. | Methods and apparatus for improved 911 support for VoIP service |
US7602886B1 (en) | 2005-07-20 | 2009-10-13 | Sprint Spectrum L.P. | Method and system for using a network-provided location for voice-over-packet emergency services calls |
CA2615894A1 (en) | 2005-07-28 | 2007-02-08 | Mformation Technologies, Inc. | System and method for service quality management for wireless devices |
US8600410B2 (en) | 2005-07-28 | 2013-12-03 | Unwired Planet, Llc | Wireless network with adaptive autonomous location push |
EP1907901B1 (en) | 2005-07-28 | 2017-01-18 | Alcatel Lucent | System and method for remotely controlling device functionality |
US20070027997A1 (en) | 2005-07-29 | 2007-02-01 | Cisco Technology, Inc. | Technique for translating location information |
US20070036139A1 (en) | 2005-08-09 | 2007-02-15 | Ashish Patel | System and method for authenticating internetwork resource requests |
KR100690877B1 (en) | 2005-08-11 | 2007-03-09 | 엘지전자 주식회사 | Periodic positioning method in mobile communication system |
GB0517064D0 (en) | 2005-08-19 | 2005-09-28 | Nokia Corp | Mobile access network server |
US20070049288A1 (en) | 2005-08-24 | 2007-03-01 | Lamprecht Leslie J | Creating optimum temporal location trigger for multiple requests |
US7245900B1 (en) | 2005-08-24 | 2007-07-17 | Sprint Spectrum L.P. | Method and system for using basic service set identifiers (BSSIDs) for emergency services routing |
US8068056B2 (en) | 2005-08-25 | 2011-11-29 | Qualcomm Incorporated | Location reporting with secure user plane location (SUPL) |
US20070081635A1 (en) | 2005-09-29 | 2007-04-12 | Marian Croak | Method and apparatus for providing enhanced 911 for nomadic users |
KR101133850B1 (en) | 2005-10-10 | 2012-04-06 | 삼성전자주식회사 | Terminal and server in location service providing system and method thereof |
AU2006225248B2 (en) | 2005-10-10 | 2007-10-18 | Samsung Electronics Co., Ltd. | Location service-providing system and deferred location request service-providing method using previously computed location in location service-providing system |
US8824454B2 (en) | 2005-10-24 | 2014-09-02 | West Corporation | Peering network for parameter-based routing of special number calls |
US7711094B1 (en) | 2005-11-16 | 2010-05-04 | Verizon Data Services Llc | E911 location server |
US8185128B2 (en) | 2005-11-30 | 2012-05-22 | Qualcomm Incorporated | Method and apparatus for supporting location services with roaming |
US8185567B2 (en) | 2006-01-02 | 2012-05-22 | Telecommunication Systems, Inc. | Location aware content using presence information data formation with location object (PIDF-LO) |
US20070160036A1 (en) | 2006-01-10 | 2007-07-12 | Smith David M | Method and system for servicing enhanced 911 calls |
US20070167177A1 (en) | 2006-01-19 | 2007-07-19 | Nokia Corporation | Terminal status discovery in secure user plane location positioning procedure |
US9112705B2 (en) | 2006-02-15 | 2015-08-18 | Nec Corporation | ID system and program, and ID method |
US8958346B2 (en) | 2006-03-02 | 2015-02-17 | Tango Networks, Inc. | Calling line/name identification of enterprise subscribers in mobile calls |
KR100880406B1 (en) | 2006-03-24 | 2009-01-30 | 엘지전자 주식회사 | Location positioning method in handover between networks |
US8208461B2 (en) | 2006-04-04 | 2012-06-26 | Telecommunication Systems, Inc. | SS7 MAP/Lg+ to SIP based call signaling conversion gateway for wireless VoIP E911 |
US8358645B2 (en) | 2006-04-14 | 2013-01-22 | Cisco Technology, Inc. | Determining a physical location of a VoIP endpoint device utilized to originate an emergency call |
US7937067B2 (en) | 2006-05-16 | 2011-05-03 | Red Sky Technologies, Inc. | System and method for an emergency location information service (E-LIS) |
US7940896B2 (en) | 2006-06-29 | 2011-05-10 | Avaya Inc. | Adaption of emergency calls to the emergency services network based on caller location |
US20080020733A1 (en) | 2006-07-21 | 2008-01-24 | Tomas Karl-Axel Wassingbo | Mobile electronic device with motion detection authentication |
US8774370B2 (en) | 2006-08-21 | 2014-07-08 | Connexon Telecom Inc. | System and method for delivering callback numbers for emergency calls in a VOIP system |
US20080065775A1 (en) | 2006-09-13 | 2008-03-13 | Cisco Technology, Inc. | Location data-URL mechanism |
US8503430B2 (en) | 2006-11-21 | 2013-08-06 | Qualcomm Incorporated | Dynamic operational mode management for a wireless terminal |
US20080214202A1 (en) | 2007-03-02 | 2008-09-04 | General Instrument Corporation | Method and Apparatus for Bluetooth Discoverability Using Region Estimation |
US8457661B2 (en) | 2007-12-12 | 2013-06-04 | Mogreet, Inc. | Methods and systems for transmitting video messages to mobile communication devices |
US8099764B2 (en) | 2007-12-17 | 2012-01-17 | Microsoft Corporation | Secure push and status communication between client and server |
UA103021C2 (en) | 2008-03-28 | 2013-09-10 | Селлтраст Корпорейшн | Systems and methods for secure short messaging service and multimedia messaging service (embodiments) |
US20090320123A1 (en) | 2008-06-20 | 2009-12-24 | Motorola, Inc. | Method and apparatus for user recognition employing motion passwords |
US8745088B2 (en) | 2009-03-27 | 2014-06-03 | Sap Ag | System and method of performing risk analysis using a portal |
US8600416B2 (en) | 2009-08-31 | 2013-12-03 | Verizon Patent And Licensing Inc. | Method and system for providing messaging gateway services |
US8704863B2 (en) | 2010-04-07 | 2014-04-22 | Apple Inc. | Transitioning between circuit switched calls and video calls |
US8792683B2 (en) | 2010-06-04 | 2014-07-29 | Blackberry Limited | Fingerprint scanning with optical navigation |
US8997196B2 (en) | 2010-06-14 | 2015-03-31 | Microsoft Corporation | Flexible end-point compliance and strong authentication for distributed hybrid enterprises |
WO2012068045A2 (en) | 2010-11-15 | 2012-05-24 | Trilliant Holdings Inc. | System and method for securely communicating across multiple networks using a single radio |
US8510820B2 (en) | 2010-12-02 | 2013-08-13 | Duo Security, Inc. | System and method for embedded authentication |
US8510398B2 (en) | 2010-12-10 | 2013-08-13 | At&T Intellectual Property I, Lp | Apparatus and method for managing message communication |
US9372979B2 (en) | 2011-01-07 | 2016-06-21 | Geoff Klein | Methods, devices, and systems for unobtrusive mobile device user recognition |
US20120192287A1 (en) | 2011-01-25 | 2012-07-26 | Yigang Cai | Text message security |
US10292066B2 (en) * | 2011-11-04 | 2019-05-14 | Cisco Technology, Inc. | System and method of modifying congestion control based on mobile system information |
JP5923982B2 (en) | 2011-12-28 | 2016-05-25 | 株式会社リコー | Mobile device, authentication method, authentication program, |
TW201334491A (en) | 2012-02-07 | 2013-08-16 | Ind Tech Res Inst | Method and device for generation of secret key |
US20130336210A1 (en) * | 2012-06-15 | 2013-12-19 | Telefonaktiebolaget L M Ericsson (Publ) | Wholesale partner and video services enablement using a mobile virtual network enabler (MVNE) |
-
2013
- 2013-10-17 US US14/056,412 patent/US9301191B2/en not_active Expired - Fee Related
-
2015
- 2015-11-30 US US14/953,758 patent/US20160192232A1/en not_active Abandoned
-
2016
- 2016-02-12 US US15/042,203 patent/US20160165480A1/en not_active Abandoned
Patent Citations (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8089986B2 (en) * | 2003-05-15 | 2012-01-03 | At&T Intellectual Property I, L.P. | Managing quality of service in a communication network for applications |
US7561586B2 (en) * | 2003-09-19 | 2009-07-14 | Nortel Networks Limited | Method and apparatus for providing network VPN services on demand |
US20070258575A1 (en) * | 2006-05-05 | 2007-11-08 | John Douglas | Number portability for an IMS network |
US8504687B2 (en) * | 2008-11-26 | 2013-08-06 | Telecom Italia S.P.A. | Application data flow management in an IP network |
US20130132854A1 (en) * | 2009-01-28 | 2013-05-23 | Headwater Partners I Llc | Service Plan Design, User Interfaces, Application Programming Interfaces, and Device Management |
US20120314632A1 (en) * | 2010-02-16 | 2012-12-13 | Pablo Martinez De La Cruz | Facilitating a communication session |
US20110219431A1 (en) * | 2010-03-04 | 2011-09-08 | Haseeb Akhtar | System and method of quality of service enablement for over the top applications in a telecommunications system |
US20110280143A1 (en) * | 2010-05-13 | 2011-11-17 | Futurewei Technologies, Inc. | System, Apparatus for Content Delivery for Internet Traffic and Methods Thereof |
US20120324100A1 (en) * | 2011-04-13 | 2012-12-20 | Interdigital Patent Holdings, Inc | Methods, systems and apparatus for managing and/or enforcing policies for managing internet protocol ("ip") traffic among multiple accesses of a network |
US20120296784A1 (en) * | 2011-05-20 | 2012-11-22 | Brenda Ann Connor | Controlling quality of service provided to over the top applications in a telecommunications system |
US20130121262A1 (en) * | 2011-11-15 | 2013-05-16 | Motorola Solutions, Inc. | Preserving user-differentiated quality of service for mobile virtual private network communications made using a shared connection point |
US20150043350A1 (en) * | 2012-03-14 | 2015-02-12 | Telefonaktiebolaget L M Ericsson (Publ) | Method for providing a qos prioritized data traffic |
US20140020060A1 (en) * | 2012-07-12 | 2014-01-16 | Verizon Patent And Licensing Inc. | Quality of service application |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160119165A1 (en) * | 2014-10-27 | 2016-04-28 | Netsnapper Technologies Sarl | Methods and systems to manage network connections |
US11765050B1 (en) | 2022-03-15 | 2023-09-19 | Cisco Technology, Inc. | Event triggered guaranteed service connectivity |
Also Published As
Publication number | Publication date |
---|---|
US20150085664A1 (en) | 2015-03-26 |
US20160192232A1 (en) | 2016-06-30 |
US9301191B2 (en) | 2016-03-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9301191B2 (en) | Quality of service to over the top applications used with VPN | |
CN109548008B (en) | Method and equipment for identifying and controlling remote user equipment by network side | |
US10616120B2 (en) | Service layer southbound interface and quality of service | |
US20140160990A1 (en) | Mechanisms for Quality of Service to Over the Top Applications for Use in Commercial Wireless Networks | |
US9112909B2 (en) | User and device authentication in broadband networks | |
KR100967749B1 (en) | Address management method, address management system, mobile terminal and home domain server | |
US11558879B2 (en) | Handling network traffic via a fixed access | |
WO2020199896A1 (en) | Service flow routing control method, apparatus and system | |
US9642032B2 (en) | Third party interface for provisioning bearers according to a quality of service subscription | |
JP5982690B2 (en) | Network convergence method, device, and communication system | |
KR20160004854A (en) | Apparatus and method for providing a service connection through access layer in wireless communication system | |
US10791464B2 (en) | Method for establishing a secure connection | |
WO2018054272A1 (en) | Data transmission method and device, and computer storage medium | |
US10897451B2 (en) | System and method for transmitting over multiple simultaneous communication networks by using point-to-point protocol over ethernet | |
JP4802238B2 (en) | How to set up a network-based tunnel for mobile terminals in a local network interconnection | |
EP3879866B1 (en) | Method for establishing a secure connection for the internet of things | |
US20230125058A1 (en) | Content service accessibility for unauthenticated users | |
US20230198862A1 (en) | Method for processing a data packet in a communication network, method for processing a request to change the quality of service level of a connection, method for requesting to change the quality of service level of a connection, method for managing a quality of service, corresponding devices, system and computer programs | |
JP2015041970A (en) | Communication system, communication method and communication program | |
EP4352922A1 (en) | System and method for establishing a dual-layer pdu session | |
KR20070028461A (en) | Binding mechanism for quality of service management in a communication network | |
WO2012083803A1 (en) | Priority inheritance method and system for quality of service in identifier network |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: TELECOMMUNICATION SYSTEMS, INC,, MARYLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SACHDEV, VINEET;MCFARLAND, KEITH;GRIFFIN, JOHN L.;SIGNING DATES FROM 20131022 TO 20151106;REEL/FRAME:037721/0662 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |