USH2051H1 - System and method for providing multiple quality of service classes - Google Patents

System and method for providing multiple quality of service classes Download PDF

Info

Publication number
USH2051H1
USH2051H1 US09/676,114 US67611400A USH2051H US H2051 H1 USH2051 H1 US H2051H1 US 67611400 A US67611400 A US 67611400A US H2051 H USH2051 H US H2051H
Authority
US
United States
Prior art keywords
quality
packet
service
terminal unit
service information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US09/676,114
Other languages
English (en)
Inventor
Yinjun Zhu
Carl Mansfield
Alan Carlton
Narayan Menon
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Opuswave Networks Inc
Original Assignee
Opuswave Networks Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Opuswave Networks Inc filed Critical Opuswave Networks Inc
Priority to US09/676,114 priority Critical patent/USH2051H1/en
Assigned to OPUSWAVE NETWORKS, INC. reassignment OPUSWAVE NETWORKS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MANSFIELD, CARL, CARLTON, ALAN, NARAYAN, MENON, ZHU, YINJUN
Priority to PCT/US2001/023625 priority patent/WO2002030056A2/fr
Priority to AU2001283001A priority patent/AU2001283001A1/en
Application granted granted Critical
Publication of USH2051H1 publication Critical patent/USH2051H1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • 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/2416—Real-time traffic
    • 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
    • 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/2441—Traffic characterised by specific attributes, e.g. priority or QoS relying on flow classification, e.g. using integrated services [IntServ]
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/563—Allocation or scheduling criteria for wireless resources based on priority criteria of the wireless resources

Definitions

  • This invention relates generally to the field of communications, and more specifically to a system and method for providing multiple quality of service classes.
  • VoIP Voice over Internet Protocol
  • IP Telephony applications analog voice signals are typically digitized, and the resulting data is segmented into packets. The packets are transmitted across the packet network to a destination node, where the packets are reassembled and the data converted back into analog signals.
  • Typical networks such as the Global System for Mobile communication General Packet Radio Services (GSM/GPRS) network, use packet data protocol (PDP) contexts to support applications executed on a terminal unit.
  • PDP packet data protocol
  • Each terminal unit uses a PDP context to support the transfer of packet data messages in the network.
  • a single PDP context may support one application or multiple applications executed by a terminal unit.
  • each PDP context is associated with a network address, such as an Internet Protocol (IP) address.
  • IP Internet Protocol
  • Typical networks also use quality of service classes to identify how well an application executed in the network performs from the subscriber's perspective.
  • quality of service classes may be based on the speed, accuracy, and dependability of the network from the subscriber's point of view. Functions like data transfer operations may operate successfully using lower quality of service classes. These applications are usually not time-sensitive, so delays in the network are acceptable.
  • real-time applications like Internet Telephony applications need higher qualities of service to perform optimally. Packets carrying digitized voice data need to arrive within a specific amount of time at the destination node. Otherwise, excessive delays reduce the quality of the voice signal that is produced at the destination node.
  • Conventional networks assign a quality of service class to each PDP context, and all applications executed by a subscriber under one PDP context receive the same quality of service class.
  • a subscriber typically establishes multiple PDP contexts, and each PDP context receives a different quality of service.
  • a problem with this approach is that conventional systems cannot differentiate between the applications executed under a single PDP context.
  • a subscriber may execute a large number of applications under one PDP context, and only a few of the applications may require a high quality of service class.
  • Conventional systems treat all of the subscriber's applications similarly, so each application receives the same quality of service class. As a result, all of the subscriber's applications may receive a high quality of service class, even though only a few of the applications actually require the high class to work optimally.
  • a similar problem exists if the PDP context handles only a low quality of service level. An application requiring a higher quality of service class will not work well.
  • Another problem with this approach is that conventional systems cannot efficiently handle the traffic for applications executed by multiple subscribers.
  • One subscriber who receives a high quality of service class may execute a large number of applications under one PDP context, and all of the applications receive the high quality of service. Because this subscriber's applications are all receiving the high quality of service, other subscribers may be unable to receive that quality of service.
  • the system may use network resources to provide all of the first subscriber's applications with the high quality of service class, even though few of the applications require it. Even if the other subscribers wish to execute real-time applications, they may be forced to use a lower quality of service because network resources are unavailable.
  • the conventional systems are unable to efficiently handle the traffic for multiple subscribers.
  • a further problem with this approach is that conventional systems assign each PDP context a separate IP address.
  • a subscriber may receive multiple quality of service classes, but the subscriber must first establish multiple PDP contexts. This forces the conventional networks to assign multiple IP addresses to a single subscriber.
  • the number of IP addresses may be limited in conventional networks, which also limits the number of PDP contexts that may be established by the subscribers in the networks. Some subscribers may be unable to receive multiple quality of services classes if the network cannot assign IP addresses to the additional PDP contexts established by the subscribers.
  • a system and method for providing multiple quality of service classes are provided that substantially reduce or eliminate disadvantages and problems associated with previously developed systems and methods.
  • a system for providing multiple quality of service classes to a subscriber using a terminal unit includes a gateway operable to communicate with a network and a base station coupled to the gateway.
  • the base station is operable to communicate with the terminal unit over a wireless interface.
  • the base station is also operable to receive a first packet associated with a first application and a second packet associated with a second application from the gateway.
  • the applications are executed by the terminal unit.
  • the base station is further operable to identify a first quality of service class associated with the first packet and a second quality of service class associated with the second packet using quality of service information.
  • the quality of service information is associated with the first and second applications, and at least a portion of the quality of service information is identified by a network address.
  • the base station is operable to communicate the first packet to the terminal unit using the first quality of service class and to communicate the second packet to the terminal unit using the second quality of service class.
  • a method for providing multiple quality of service classes to a subscriber using a terminal unit includes receiving a first packet associated with a first application and a second packet associated with a second application, where the applications are executed by the terminal unit. The method also includes identifying a first quality of service class associated with the first packet and a second quality of service class associated with the second packet using quality of service information. The quality of service information is associated with the first and second applications, and at least a portion of the quality of service information is identified by a network address. The method further includes communicating the first packet over a wireless interface using the first quality of service class, and communicating the second packet over the wireless interface using the second quality of service class.
  • a communications system differentiates between the applications executed by a subscriber under a single packet data protocol (PDP) context.
  • Applications that are executed by the same subscriber under one PDP context may receive different quality of service classes. For example, real-time applications may receive higher qualities of service, while data transfer applications executed under the same PDP context receive lower qualities of service. This allows each application executed by the subscriber to receive an appropriate quality of service.
  • PDP packet data protocol
  • Another technical advantage is the ability to handle traffic for applications executed by multiple subscribers more efficiently.
  • Each application under a PDP context may have a corresponding quality of service class, which allows the system to limit the high quality of service to applications that actually need it. Rather than providing the high quality of service to all applications executed by a limited number of subscribers, the system may be able to provide the high quality of service class to a larger number of subscribers. By establishing a quality of service class for each application, traffic for multiple subscribers executing multiple applications may be handled more effectively.
  • a subscriber may receive multiple quality of service classes without forcing the communications system to assign multiple network addresses to the subscriber.
  • a subscriber may establish a single PDP context and receive multiple quality of service classes. The subscriber is not required to establish multiple PDP contexts, so the system is not forced to assign multiple network addresses, such as Internet Protocol (IP) addresses, to each subscriber. The system remains free to assign the IP addresses to other elements in system 10 . This also allows the system to provide multiple quality of service classes to any number of subscribers. The system may not be limited by the number of available IP addresses.
  • IP Internet Protocol
  • FIG. 1 is a block diagram illustrating an exemplary communications system
  • FIG. 2 is a block diagram illustrating an exemplary voice transmission plane in the communications system of FIG. 1;
  • FIG. 3 is a block diagram illustrating an exemplary subnetwork dependent convergence protocol (SNDCP) layer providing multiple quality of service classes to subscribers in the communications system of FIG. 1;
  • SNDCP subnetwork dependent convergence protocol
  • FIG. 4 is a block diagram illustrating the SNDCP layer of the communications system of FIG. 1;
  • FIG. 5 is a block diagram illustrating an exemplary entry in a state table in the communications system of FIG. 1;
  • FIG. 6 is a flow diagram illustrating an exemplary method for providing multiple quality of service classes to a subscriber.
  • FIG. 7 is a flow diagram illustrating an exemplary method for performing snooping operations to provide multiple quality of service classes to a subscriber.
  • FIGS. 1 through 10 of the drawings like numerals being used for like and corresponding parts of the various drawings.
  • FIG. 1 is a block diagram illustrating an exemplary communications system 10 .
  • system 10 comprises a plurality of terminal units 12 , a base station (BTS) 14 , an access router 16 , a private packet network 18 , a network management system 20 , a circuit-switched gateway 22 , a gatekeeper 24 , and a packet-switched gateway 26 .
  • BTS base station
  • Other embodiments of system 10 may be used without departing from the scope of the present invention.
  • the present invention may be implemented in any system that supports quality of service classes.
  • GSM/EDGE Global System for Mobile communication Enhanced Data rate for Global Evolution
  • GSM/GPRS GSM General Packet Radio Services
  • WCDMA Wideband Code Division Multiple Access
  • CDPD Cellular Digital Packet Data
  • PDS Packet Data Services
  • System 10 includes two planes of operation.
  • One plane is a transmission plane, and the other plane is a signaling plane.
  • the transmission plane transports packets that contain voice, fax, and data traffic
  • the signaling plane carries control messages used to establish, maintain, and release connections in system 10 .
  • Each plane may also be subdivided to deal with packets carrying traffic to and from a packet network, and packets carrying traffic to and from an analog network.
  • a terminal unit 12 executes one or more applications, and terminal unit 12 establishes a packet data protocol (PDP) context to support the transmission of data packets to and from the applications in system 10 .
  • PDP packet data protocol
  • Terminal unit 12 and base station 14 also establish quality of service classes for the applications that use the PDP context.
  • terminal unit 12 and base station 14 perform multiplexing and demultiplexing operations, called “snooping operations,” to allow the applications executed under the PDP context to receive different quality of service classes.
  • system 10 may handle traffic for terminal units 12 running multiple applications more effectively.
  • Each terminal unit 12 communicates with base station 14 over a wireless interface 28 .
  • Terminal unit 12 provides packet voice, fax, and/or data services to a subscriber of system 10 by executing applications and exchanging packets of data with base station 14 .
  • Terminal unit 12 also establishes one or more PDP contexts to support the transmission of the packets in system 10 .
  • Each PDP context established by terminal unit 12 may be uniquely identified in system 10 by a network address, such as an Internet Protocol (IP) address.
  • IP Internet Protocol
  • Each application executed on a terminal unit 12 may also be identified, for example, by a Transmission Control Protocol (TCP) or a User Datagram Protocol (UDP) port number.
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • system 10 uses the International Telecommunications Union-Telecommunications (ITU-T) H.323 standard to transport voice traffic
  • terminal unit 12 appears as a H.323 terminal in system 10 .
  • Terminal unit 12 may comprise any device capable of communicating with base station 14 over wireless interface 28 .
  • Terminal unit 12 could, for example, include a memory, a transmitter, and logic encoded in hardware, software, and/or firmware that configures the memory and/or transmitter as a terminal unit 12 .
  • terminal unit 12 comprises a computer 30 coupled to a wireless modem 32 .
  • Computer 30 may support packet data, fax, and/or voice applications executed by the subscriber.
  • a telephone 34 or a fax machine could also be coupled to computer 30 .
  • Other embodiments of terminal unit 12 may be used without departing from the scope of the present invention.
  • terminal unit 12 could also comprise a mobile telephone, such as a GSM mobile station.
  • Wireless interface 28 communicatively couples terminal unit 12 and base station 14 .
  • the term “wireless” designates the use of a radio or over-the-air interface to communicate with terminal unit 12 .
  • Wireless interface 28 may comprise any suitable circuit-switched or packet-switched wireless interface.
  • Wireless interface 28 may, for example, comprise a GSM/EDGE interface.
  • Base station 14 is coupled to access router 16 .
  • the term “couple” refers to any direct or indirect connection between two or more elements in system 10 , whether or not those elements physically contact one another.
  • Base station 14 provides bi-directional communication with one or more terminal units 12 in a specified geographic area. For example, base station 14 transmits and receives packet messages to and from terminal units 12 over wireless interface 28 . Base station 14 transmits and receives packet messages to and from private network 18 through access router 16 .
  • Each base station 14 may be uniquely identified in system 10 by a network address, such as an IP address, and the network address may be statically or dynamically assigned.
  • Base station 14 may comprise any suitable device operable to facilitate communication with terminal units 12 .
  • Base station 14 may, for example, comprise one or more radio transceivers capable of transmitting packet-switched messages to and receiving messages from terminal unit 12 over wireless interface 28 .
  • Base station 14 could also include a memory and logic encoded in hardware, software, and/or firmware that configures the memory and/or the transmitters as a base station 14 .
  • Access router 16 is coupled to base station 14 and private network 18 . Access router 16 routes packets containing voice, fax, and/or data traffic in system 10 . Access router 16 receives packets from base station 14 and routes the packets over private network 18 . Access router 16 also receives packets from private network 18 for a terminal unit 12 served by base station 14 , and access router 16 routes the packets to base station 14 . Access router 16 may comprise any suitable device operable to route messages over private network 18 . Access router 16 could, for example, comprise a wireless router and concentrator.
  • Private network 18 is coupled to access router 16 , network management system 20 , circuit-switched gateway 22 , gatekeeper 24 , and packet-switched gateway 26 .
  • Private network 18 facilitates communication between components in system 10 by transferring messages between the components.
  • Private network 18 may comprise any suitable packet network, such as a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), or any other communications system or systems at one or multiple locations.
  • LAN local area network
  • MAN metropolitan area network
  • WAN wide area network
  • Network management system 20 provides management functionality in system 10 .
  • Network management system 20 communicates with other components in system 10 and transmits management messages to the components.
  • Network management system 20 also receives messages and responses from the components in system 10 .
  • network management system 20 comprises a subscriber management platform (SMP) 36 and an operations support system (OSS) 38 .
  • SMP subscriber management platform
  • OSS operations support system
  • SMP 36 is coupled to private network 18 .
  • SMP 36 provides subscriber management and billing functionality in system 10 . This may include, for example, authentication functionality to protect against fraud and customer registration functionality to collect customer data used in provisioning services and billing customers. This may also include rating functionality to create flexible pricing plans for subscribers, billing functionality to generate real-time or invoice customer bills, and customer management functionality to provide access to customer profiles, activities, and account balances.
  • SMP 36 may comprise any suitable device operable to provide subscriber management functionality.
  • terminal unit 12 and base station 14 communicate with SMP 36 to retrieve subscriber profile information from SMP 36 .
  • Terminal unit 12 and base station 14 use the subscriber profile information to authenticate a terminal unit and provide quality of service classes to a subscriber.
  • terminal unit 12 and base station 14 use a terminal management protocol (TMP), and base station 14 and SMP 36 use a Remote Authentication Dial In User Service (RADIUS) protocol.
  • TMP terminal management protocol
  • RADIUS Remote Authentication Dial In User Service
  • OSS 38 is coupled to private network 18 .
  • OSS 38 provides network management functionality the manage the components in system 10 . This may include, for example, provisioning, administration, status, and performance monitoring functionality for the network components in system 10 . This may also include configuration, fault, and security management.
  • OSS 38 may comprise any suitable device operable to provide network management functionality. In one embodiment, OSS 38 may be identified by a network address, such as a statically or dynamically assigned IP address.
  • Circuit-switched gateway 22 is coupled to private network 18 , gatekeeper 24 , and a public switched circuit network (SCN) 40 .
  • SCN 40 may comprise any suitable circuit-switched network, such as a public switched telephone network (PSTN) or an integrated services digital network (ISDN).
  • PSTN public switched telephone network
  • ISDN integrated services digital network
  • Gateway 22 facilitates communication between system 10 and SCN 40 by transferring messages between private network 18 and SCN 40 .
  • Gateway 22 also performs an interworking function to translate between the packet-switched signaling and transmission protocols used by private network 18 and the circuit-switched protocols used by SCN 40 .
  • system 10 uses the protocols defined by the ITU-T H.323 standard, and gateway 22 interworks the H.323 signaling protocols with the circuit switched protocols of SCN 40 .
  • Gateway 22 may comprise any suitable device operable to facilitate communication between system 10 and SCN 40 .
  • Gateway 22 may, for example, comprise an H.323 gateway.
  • Gatekeeper 24 is coupled to private network 18 , circuit-switched gateway 22 , and packet-switched gateway 26 .
  • Gatekeeper 24 provides call control services in system 10 . This may include, for example, tracking the location of each terminal unit 12 and routing messages to and from the base station 14 currently serving a particular terminal unit 12 . This may also include address translation to map between the telephone number and current IP address of a terminal unit 12 .
  • Gatekeeper 24 may comprise any suitable device operable to provide call control services in system 10 . In one embodiment, gatekeeper 24 comprises an H.323 gatekeeper.
  • Packet-switched gateway 26 is coupled to private network 18 , gatekeeper 24 , and a public packet-switched network 42 .
  • Public packet-switched network 42 may comprise any suitable packet-switched network, such as the Internet, a LAN, a MAN, a WAN, or any other communications system or systems in one or multiple locations.
  • Packet-switched gateway 26 facilitates communication between system 10 and public network 42 by transferring messages between private network 18 and public network 42 .
  • Gateway 26 may comprise any suitable device operable to facilitate communication between system 10 and public network 42 .
  • Gateway 26 may, for example, comprise an access router that supports routing and firewalling functionality.
  • FIG. 1 illustrates one embodiment of system 10
  • numerous changes may be made to system 10 without departing from the scope of the present invention.
  • multiple base stations 14 may be used in system 10 .
  • gateway 22 and gatekeeper 24 are illustrated as separate units, gateway 22 and gatekeeper 24 may also be contained in one physical node.
  • FIG. 2 is a block diagram illustrating an exemplary voice transmission plane in communications system 10 of FIG. 1 .
  • the packet data transmission plane comprises a computer/terminal protocol stack 60 , a wireless modem (WM) protocol stack 100 , a base station protocol stack 140 , an access router protocol stack 180 , and a circuit-switched gateway protocol stack 240 .
  • WM wireless modem
  • Other embodiments of the voice transmission plane may be used in system 10 without departing from the scope of the present invention.
  • Computer/terminal protocol stack 60 comprises a physical link layer 62 , a modem command layer 64 , an Internet Protocol (IP) layer 66 , a UDP layer 68 , a Realtime Transfer Protocol (RTP) layer 70 , and a vocoder layer 72 .
  • Wireless modem protocol stack 100 comprises a physical link layer 102 , a modem command layer 104 , a relay 106 , a subnetwork dependent convergence protocol (SNDCP) layer 108 , a logical link control (LLC) layer 110 , a radio link control (RLC) layer 112 , a medium access control (MAC) layer 114 , and a physical (PHL) layer 116 .
  • SNDCP subnetwork dependent convergence protocol
  • LLC logical link control
  • RLC radio link control
  • MAC medium access control
  • PHL physical
  • Base station protocol stack 140 comprises a physical layer 142 , a MAC layer 144 , a RLC layer 146 , a LLC layer 148 , a SNDCP layer 150 , a relay 152 , a frame relay layer 154 , and a T1 layer 156 .
  • Access router protocol stack 180 comprises a T1 layer 182 , a frame relay layer 184 , an IP layer 186 , an Ethernet layer 188 , and a 10-base-T layer 190 .
  • Circuit-switched gateway protocol stack 240 comprises a 10-base-T layer 242 , an Ethernet layer 244 , an IP layer 246 , a UDP layer 248 , a RTP layer 250 , and a vocoder layer 252 .
  • Physical link layers 62 and 102 manage the interface between computer 30 and wireless modem 32 .
  • Physical link layers 62 and 102 may, for example, support a personal computer memory card international association (PCMCIA) interface.
  • Modem command layers 64 and 104 support control of wireless modem 32 by computer 30 .
  • computer 30 controls wireless modem 32 using an AT command set.
  • terminal unit 12 uses an AT command set based on the GSM 07.60 standard, entitled “Mobile Station (MS) Supporting GPRS.”
  • Vocoder layers 74 and 252 support vocoding functions in terminal unit 12 and circuit-switched gateway 22 .
  • terminal units 12 have an audio codec to encode and decode voice traffic.
  • Terminal units 12 may support a variety of coding standards, including ITU-T Recommendations G.711, G.722, G.728, G.729, and G.723.1, as well as MPEG 1 audio and GSM Full Rate, Half Rate and Enhanced Full Rate vocoders.
  • RTP layers 72 and 250 , UDP layers 70 and 248 , and IP layers 66 , 186 , and 246 support the transport of voice traffic between terminal unit 12 and circuit-switched gateway 22 .
  • the encoded voice traffic may be transmitted between terminal unit 12 and gateway 22 in RTP packets carried over a UDP/IP connection. Transmission of the RTP packets may also be supplemented by the RTP Control Protocol (RTCP) to provide control and identification functionality in system 10 .
  • RTCP RTP Control Protocol
  • Relay 106 transfers packet data messages between the interface with computer 30 and the interface with base station 14 . This may include, for example, transferring packet messages between a PCMCIA interface and SNDCP layer 108 .
  • SNDCP layers 108 and 150 map data packets containing voice, fax, and traffic onto LLC frames for transport between terminal unit 12 and base station 14 .
  • SNDCP layers 108 and 150 also perform encryption, header compression, and data compression.
  • LLC layers 110 and 148 provide a reliable ciphered logical link between terminal unit 12 and base station 14 , and the packet data messages are transferred between LLC layers 110 and 148 in LLC frames.
  • RLC layers 112 and 146 and MAC layers 114 and 144 support the transfer of information over wireless interface 28 .
  • RLC layers 112 and 146 and MAC layers 114 and 144 may, for example, map LLC frames from LLC layers 110 and 148 onto RLC data blocks transmitted over wireless interface 28 .
  • Physical layers 116 and 142 manage wireless interface 28 between terminal unit 12 and base station 14 .
  • Relay 152 transfers packet messages between the wireless interface with terminal unit 12 and the interface with access router 16 . This may include, for example, transferring packet messages between SNDCP layer 150 and frame relay layer 154 .
  • a temporary logical link identity (TLLI) is assigned to each wireless modem 32 in LLC layer 148
  • a switched virtual circuit (SVC) is established for each wireless modem 32 in frame relay layer 154 .
  • relay 152 also provides a bridging function between the TLLIs and the SVCs to provide address resolution between the two identities established for each wireless modem 32 .
  • Frame relay layers 154 and 184 provide a link layer transport protocol between base station 14 and access router 16 to transport packet messages between base station 14 and access router 16 .
  • T1 layers 156 and 182 support the physical interface between base station 14 and access router 16 .
  • Ethernet layers 188 and 244 provide a transport protocol between access router 16 and circuit-switched gateway 22 .
  • Ethernet layers 188 and 244 transport packet messages between access router 16 and circuit-switched gateway 22 .
  • 10-base-T layers 190 and 242 support the physical interface between access router 16 and circuit-switched gateway 22 .
  • LLC layers 110 and 148 support different quality of service classes in system 10 .
  • SNDCP layers 108 and 150 perform snooping operations to provide a quality of service class to each application executed by a terminal unit 12 .
  • FIG. 2 only illustrates the voice transmission plane, LLC layers 110 and 148 and SNDCP layers 108 and 150 may also be used in the voice signaling plane and the packet data planes.
  • FIG. 3 is a block diagram illustrating an exemplary subnetwork dependent convergence protocol (SNDCP) layer 150 providing multiple quality of service classes to subscribers in communications system 10 of FIG. 1 .
  • SNDCP subnetwork dependent convergence protocol
  • FIG. 3 is described with respect to SNDCP layer 150 in base station 14
  • SNDCP layer 108 in terminal unit 12 may be the same or similar to SNDCP layer 150 .
  • LLC layer 148 provides the different quality of service classes in system 10 .
  • the different quality of service classes may, for example, use different reliability, delay, precedence, mean throughput, and peak throughput parameters.
  • the reliability parameter establishes data transfer requirements to transport packets in system 10 , such as whether to use acknowledged TCP/IP or unacknowledged UDP/IP transfer mode.
  • the delay parameter specifies the latency, or delay, that occurs when transporting packets in system 10 .
  • the precedence parameter defines a priority level used to provision services to subscribers, and system 10 provides services to applications with higher priorities sooner than applications with lower priorities.
  • the mean throughput parameter identifies the average amount of data that may be transported in system 10
  • the peak throughput parameter identifies the maximum rate at which data may be transferred in system 10 .
  • LLC layer 148 uses Service Access Point Identifiers (SAPIs) 408 to identify the different quality of service classes supported in system 10 .
  • SAPIs Service Access Point Identifiers
  • LLC layer 148 uses four SAPIs 408
  • LLC layer 148 provides four different quality of service classes.
  • Other embodiments of LLC layer 148 may be used without departing from the scope of the present invention.
  • system 10 supports three quality of service classes. One class supports real-time, reliable transport of voice traffic, and a second class supports non-real-time, unreliable transport of packet data. A third class supports non-real-time transport of signaling messages in system 10 .
  • SNDCP layer 150 provides a quality of service class to each application executed on terminal unit 12 by performing snooping operations. To perform the snooping operations, SNDCP layer 150 identifies the quality of service class assigned to an application executed on terminal unit 12 . After identifying the quality of service class for the application, SNDCP layer 150 routes a packet to the SAPI 408 in LLC layer 148 that supports the identified quality of service.
  • SNDCP layer 150 may access a PDP context 406 that the application uses to communicate in system 10 .
  • a subscriber establishes a PDP context 406 to support the transmission of packets between terminal unit 12 and components in system 10 .
  • the PDP context 406 contains quality of service parameters for the applications executed by terminal unit 12 .
  • a PDP context 406 may support one application or multiple applications executed by terminal unit 12 .
  • SNDCP layer 150 uses Network Service Access Point Identifiers (NSAPIs) 410 to identify different PDP contexts 406 .
  • SNDCP layer 150 may use NSAPIs 410 to access a PDP context 406 and retrieve quality of service parameters for an application. After identifying the quality of service class assigned to the application, SNDCP layer 150 communicates the packet to LLC layer 148 through the SAPI 408 that supports the identified quality of service. LLC layer 148 communicates the packet to terminal unit 12 using the identified quality of service.
  • NSAPIs Network Service Access Point Identifiers
  • NSAPIs 410 identify three different PDP contexts 406 .
  • NSAPI 410 a identifies PDP context 406 a
  • NSAPI 410 b identifies PDP context 406 b
  • NSAPI 410 c identifies PDP context 406 c.
  • SNDCP layer 150 provides multiple quality of service classes to PDP contexts 406 a and 406 c and one quality of service class to PDP context 406 b.
  • PDP context 406 a receives service from SAPIs 408 a and 408 b
  • PDP context 406 c receives service from SAPI 408 b and 408 d.
  • PDP context 406 b only receives service from SAPI 408 c.
  • SNDCP layer 150 may receive a packet for an application that uses PDP context 406 a, and SNDCP layer 150 determines which quality of service the application is entitled to receive. SNDCP layer 150 then routes the packet to either SAPI 408 a or 408 b. Similarly, SNDCP layer 150 may receive a packet for an application that uses PDP context 406 c, and SNDCP layer 150 routes the packet to either SAPI 408 b or 408 d. When SNDCP layer 150 receives a packet for an application under PDP context 406 b, SNDCP layer 150 routes the packet to SAPI 408 c.
  • System 10 may configure NSAPIs 410 to identify PDP contexts 406 in any suitable manner.
  • System 10 may also link NSAPIs 410 and SAPIs 408 in any suitable manner to provide appropriate quality of service classes to different PDP contexts 406 .
  • FIG. 4 is a block diagram illustrating the SNDCP layer 150 of communications system 10 of FIG. 1 .
  • SNDCP layer 150 comprises a snooping module 400 and a management entity 402 .
  • Snooping module 400 communicates with a memory 404 in base station 14 to provide quality of service classes to applications executed by terminal units 12 .
  • Other embodiments of SNDCP layer 150 may be used without departing from the scope of the present invention.
  • FIG. 4 is described with respect to base station 14 , terminal unit 12 may be the same or similar to base station 14 .
  • Snooping module 400 in SNDCP layer 150 provides a quality of service class to each application executed on terminal unit 12 by performing snooping operations. To perform the snooping operations, snooping module 400 identifies the quality of service class that is used to transport a packet to an application executed on terminal unit 12 . Snooping module 400 may access PDP contexts 406 and/or a state table 412 , which are stored in memory 404 . PDP contexts 406 and state table 412 contain quality of service information for applications executed by terminal unit 12 . After identifying the quality of service class for the application, snooping module 400 routes the packet to the SAPI 408 in LLC layer 148 that supports the identified quality of service.
  • snooping entity 400 may access a PDP context 406 and/or state table 412 in memory 404 .
  • the PDP context 406 established by a terminal unit 12 is stored in terminal unit 12 and in memory 404 in base station 14 , and each PDP context 406 is identified in system 10 by a network address, such as an IP address.
  • Snooping module 400 uses NSAPIs 410 to access a PDP context 406 in memory 404 and retrieve quality of service parameters for an application.
  • Snooping module 400 may also access state table 412 in memory 404 and retrieve quality of service parameters for the application.
  • One embodiment of state table 412 is shown in FIG. 5, which is described below.
  • snooping module 400 After identifying an application's quality of service, snooping module 400 performs snooping operations to provide the identified quality of service class to the application. Using the quality of service information retrieved from state table 412 or PDP context 406 , snooping module 400 stamps the packet with the quality of service parameters that are used to transport the packet to terminal unit 12 . Using the stamp, snooping module 400 routes the packet to the SAPI 408 that supports the application's quality of service, and LLC layer 148 receives the packet and places the packet in an LLC frame. After passing through LLC layer 148 , the packet is transmitted to terminal unit 12 by a transmitter 414 in base station 14 .
  • Snooping module 400 may also receive a data packet from an application executed on terminal unit 12 over wireless interface 28 .
  • the packet from terminal unit 12 arrives in an LLC frame, and the LLC frame is identified by one of the SAPIs 408 .
  • Snooping module 400 uses SAPI 408 to identify the quality of service class assigned to the packet, and snooping module 400 communicates the packet through system 10 using that quality of service.
  • Management entity 402 is coupled to snooping module 400 .
  • Management entity 402 is operable to control snooping module 400 .
  • Management entity 400 may, for example, inform snooping entity 400 when another PDP context 406 is activated or deactivated.
  • Management entity 402 may comprise any suitable device operable to manage snooping module 400 .
  • Memory 404 is coupled to snooping entity 400 .
  • Memory 400 is operable to store PDP contexts 406 and state table 412 , which contain quality of service information for different applications executed by terminal units 12 .
  • Memory 404 is also operable to facilitate retrieval of the information in PDP contexts 406 and state table 412 by snooping module 400 .
  • Memory 404 may comprise any suitable memory operable to store quality of service information.
  • State table 412 stores quality of service information for applications that have previously received packet messages from base station 412 .
  • snooping module 400 accesses state table 412 to locate quality of service information for the application. If snooping module 400 fails to find quality of service information for the application in state table 12 , snooping module 400 accesses the PDP context 406 and retrieves the quality of service information for the application. Snooping module 400 stores the quality of service information in state table 412 , and snooping module 400 communicates the first packet to LLC layer 148 through the appropriate SAPI 408 .
  • snooping module 400 uses the quality of service information in state table 412 to communicate the packets to the appropriate SAPI 408 .
  • snooping module 400 uses state table 412 to store the connection states of applications that use the TCP/IP transfer mode and the stream states of applications that use the UDP/IP transfer mode.
  • Transmitter 414 is operable to communicate with terminal unit 12 over wireless interface 28 .
  • transmitter 414 may transmit packets to terminal unit 12 .
  • Transmitter 414 may include any suitable device operable to transmit packets to terminal unit 12 .
  • Transmitter 414 includes transceivers that are operable to transmit packets to and receive packets from terminal unit 12 .
  • FIG. 5 is a block diagram illustrating an exemplary entry 450 in state table 412 in communications system 10 of FIG. 1 .
  • State table 412 may comprise a plurality of entries 450 , and each entry 450 includes an index 452 , a quality of service identifier (QOS ID) 454 , a source IP address 456 , a source TCP/UDP port number 458 , a destination IP address 460 , and a destination TCP/UDP port number 462 .
  • QOS ID quality of service identifier
  • Other embodiments of entry 450 may be used without departing from the scope of the present invention.
  • Quality of service identifier 454 identifies one or more quality of service parameters that an application associated with entry 450 may receive in system 10 .
  • Quality of service identifier 454 may, for example, identify the delay parameter associated with the quality of service class that the application receives in system 10 .
  • Source IP address 456 identifies the IP address of the terminal unit 12 executing the application associated with entry 450
  • source TCP/UDP port number 458 identifies the TCP or UDP port number of the application.
  • Destination IP address 460 identifies the IP address of the destination in system 10 that is receiving the packet message from the application.
  • the destination may, for example, be another terminal unit 12 , circuit-switched gateway 22 , or packet-switched gateway 26 .
  • Destination TCP/UDP port number 462 identifies the TCP or UDP port number of an application at the destination that is receiving the packet.
  • Snooping module 400 When snooping module 400 receives a packet for an application, snooping module 400 accesses state table 412 . Snooping module 400 extracts the source and destination IP addresses and TCP or UDP port numbers from the packet. Snooping module 400 compares the extracted information to the entries 450 in state table 412 . If snooping module 400 identifies an entry 450 , snooping module 400 uses the quality of service identifier 454 in entry 450 to determine the quality of service class used to communicate the packet to terminal unit 12 . Otherwise, snooping module 400 accesses the PDP context 406 that corresponds to the application.
  • Snooping module 400 may, for example, use the IP addresses associated with the PDP contexts 406 to identify the application's PDP context 406 . Using PDP context 406 , snooping module 400 identifies the quality of service class for the application. Snooping module 400 also stores the information from PDP context 406 in a new entry 450 in state table 412 . When additional packets arrive for the application, snooping module 400 uses the new entry 450 in state table 412 to communicate the packets to terminal unit 12 .
  • FIG. 6 is a flow diagram illustrating an exemplary method for providing multiple quality of service classes to a subscriber.
  • a subscriber using a terminal unit 12 establishes a PDP context 406 at a step 500 . This may include, for example, establishing the throughput parameter(s) in PDP context 406 using conventional PDP context setup procedures.
  • the subscriber executes a first application at a step 502 .
  • the quality of service class for the first application is established at a step 504 . This may include, for example, terminal unit 12 receiving a packet from the first application and identifying the quality of service class using state table 412 and/or PDP context 406 .
  • the subscriber executes a second application at a step 506 .
  • the second application may be executed under the same PDP context 406 as the first application.
  • the quality of service class for the second application is established at step 508 . This may include, for example, terminal unit 12 receiving a packet from the second application and identifying the quality of service class using state table 412 and/or PDP context 406 .
  • the quality of service class for the second application may be the same as the quality of service class of the first application, or the second class may be different than the first class.
  • snooping module 400 performs snooping operations.
  • FIG. 7 is a flow diagram illustrating an exemplary method for performing snooping operations to provide multiple quality of service classes to a subscriber.
  • the quality of service classes in system 10 include reliability and delay parameters, and the illustrated method dynamically establishes the reliability and delay parameters for a packet.
  • SNDCP layer 108 in terminal unit 12 the same or similar method may be used by SNDCP layer 150 in base station 14 .
  • Terminal unit 12 receives a packet from an application executed on terminal unit 12 at a step 600 .
  • Terminal unit 12 determines whether the packet is a TCP packet at a step 602 . This may include, for example, snooping module 400 examining a header in the packet. If the packet is a TCP packet, snooping module 400 stamps the packet as a reliable TCP packet at a step 604 . This establishes the reliability parameter used to define a quality of service class in system 10 . Snooping module 400 stamps the packet as reliable because terminal unit 12 receives a confirmation over a TCP/IP connection when the packet arrives successfully at its destination. Otherwise, snooping module 400 stamps the packet as an unreliable UDP packet at a step 606 . UDP packets are stamped as unreliable since no confirmation may be received.
  • snooping module 400 determines if a connection state exists between the source and destination TCP/IP addresses contained in the packet at a step 608 . This may include, for example, snooping module 400 accessing state table 412 and determining if an entry 450 matches the source and destination IP addresses and TCP ports contained in the packet. If snooping module 400 locates a matching entry 450 , a connection state exists between the source and destination addresses, and snooping module 400 stamps the packet with the quality of service information recorded for this connection state at a step 610 .
  • This may include, for example, snooping module 400 retrieving the quality of service identifier 454 from entry 450 , and snooping module 400 stamping the packet with the delay parameter identified by entry 450 .
  • SNDCP layer 108 communicates the packet to base station 14 at a step 628 .
  • This may include, for example, snooping module 400 using the reliability and delay parameters to communicate the packet to the appropriate SAPI 408 in LLC layer 148 .
  • snooping module 400 compares the TCP port contained in the packet to TCP ports of known applications at a step 612 . This may include, for example, snooping module 400 accessing PDP context 406 in memory 404 and comparing the TCP port in the packet to the TCP ports of the applications that are executed using PDP context 406 . When snooping module 400 locates a known application with a matching TCP port, snooping module 400 stamps the packet with the quality of service information stored in PDP context 406 for this application at a step 614 . Snooping module 400 updates state table 412 at a step 616 .
  • This may include, for example, snooping module 400 storing the source and destination TCP/IP addresses of the packet and the quality of service information for the application in state table 412 .
  • SNDCP layer 108 communicates the packet to base station 14 at step 628 .
  • snooping module 400 determines if a stream state exists between the source and destination UDP/IP addresses contained in the packet at a step 618 . This may include, for example, snooping module 400 accessing state table 412 and determining if an entry 450 matches the source and destination IP addresses and UDP ports contained in the packet. If snooping module 400 locates a matching entry 450 , a stream state exists between the source and destination addresses. Snooping module 400 stamps the packet with the quality of service information recorded for this stream state at a step 620 . This may include, for example, retrieving the quality of service identifier 454 from entry 450 . SNDCP layer 108 communicates the packet to base station 14 at step 628 .
  • snooping module 400 compares the UDP port contained in the packet to UDP ports of known applications at a step 622 . This may include, for example, snooping module 400 accessing PDP context 406 in memory 404 and comparing the UDP port in the packet to the UDP ports of the applications that are executed using PDP context 406 . When snooping module 400 locates a known application with a matching UDP port, snooping module 400 stamps the packet with the quality of service information stored in PDP context 406 for this application at a step 624 . Snooping module 400 updates state table 412 at a step 626 .
  • This may include, for example, snooping module 400 storing the source and destination UDP/IP addresses for the packet and the quality of service information for the application in state table 412 .
  • SNDCP layer 108 communicates the packet to base station 14 at step 628 .
  • FIG. 7 illustrates one exemplary method for performing snooping operations to provide multiple quality of service classes to a subscriber in system 10
  • snooping module 400 may update state table 412 before stamping the packet with the quality of service information stored in PDP context 406 .
  • terminal unit 12 may support other transmission protocols in addition to or in place of the TCP/IP and UDP/IP protocols, and SNDCP layer 108 may stamp the packets with appropriate reliability and delay parameters.
  • SNDCP layer 108 may also perform TCP/IP header compression functions, and SNDCP layer 108 may merge the snooping method illustrated in FIG. 7 with the TCP/IP header compression algorithm.
  • the snooping method and compression algorithm both check the header of a packet, such as in step 602 in FIG. 7 . Combining the snooping method and compression algorithm may reduce the overall time needed to perform both functions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
US09/676,114 2000-09-29 2000-09-29 System and method for providing multiple quality of service classes Abandoned USH2051H1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US09/676,114 USH2051H1 (en) 2000-09-29 2000-09-29 System and method for providing multiple quality of service classes
PCT/US2001/023625 WO2002030056A2 (fr) 2000-09-29 2001-07-26 Systeme et procede permettant de fournir de multiples qualites de categories de services
AU2001283001A AU2001283001A1 (en) 2000-09-29 2001-07-26 System and method for providing multiple quality of service classes

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US09/676,114 USH2051H1 (en) 2000-09-29 2000-09-29 System and method for providing multiple quality of service classes

Publications (1)

Publication Number Publication Date
USH2051H1 true USH2051H1 (en) 2002-11-05

Family

ID=24713276

Family Applications (1)

Application Number Title Priority Date Filing Date
US09/676,114 Abandoned USH2051H1 (en) 2000-09-29 2000-09-29 System and method for providing multiple quality of service classes

Country Status (3)

Country Link
US (1) USH2051H1 (fr)
AU (1) AU2001283001A1 (fr)
WO (1) WO2002030056A2 (fr)

Cited By (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030081599A1 (en) * 2001-10-30 2003-05-01 Chui-Tsang Wu System and method for data transmission control
US20030083041A1 (en) * 2001-11-01 2003-05-01 Intel Corporation System and method for providing cost of quality of service levels in a wireless communication device
US20030115515A1 (en) * 2001-12-13 2003-06-19 Curtis Chris B. Method and apparatus for testing digital channels in a wireless communication system
US20030145098A1 (en) * 2002-01-25 2003-07-31 Litwin Louis Robert Adaptive cost of service for communication network based on level of network congestion
US20030187972A1 (en) * 2002-03-21 2003-10-02 International Business Machines Corporation Method and system for dynamically adjusting performance measurements according to provided service level
US20030187828A1 (en) * 2002-03-21 2003-10-02 International Business Machines Corporation Method and system for dynamically adjusting performance measurements according to provided service level
US20040063497A1 (en) * 2002-09-30 2004-04-01 Kenneth Gould Gaming server providing on demand quality of service
US20050007981A1 (en) * 2003-07-11 2005-01-13 Nokia Corporation Method and apparatus for use by a GPRS device in responding to change in SAPI connection
US20050053003A1 (en) * 2003-09-09 2005-03-10 Harris Corporation Mobile ad hoc network (MANET) with quality-of-service (QoS) protocol hierarchy and related methods
US20050053094A1 (en) * 2003-09-09 2005-03-10 Harris Corporation Mobile ad hoc network (MANET) providing quality-of-service (QoS) based unicast and multicast features
US20050054346A1 (en) * 2003-09-09 2005-03-10 Harris Corporation, Corporation Of The State Of Delaware Load leveling in mobile ad-hoc networks to support end-to-end delay reduction, QoS and energy leveling
US20050053007A1 (en) * 2003-09-09 2005-03-10 Harris Corporation Route selection in mobile ad-hoc networks based on traffic state information
US20050053005A1 (en) * 2003-09-09 2005-03-10 Harris Corporation Mobile ad hoc network (MANET) providing connectivity enhancement features and related methods
WO2005041446A1 (fr) * 2003-09-30 2005-05-06 Thomson Licensing S.A. Qualite de controle de service dans un reseau local sans fil (lan)
US20050160287A1 (en) * 2004-01-16 2005-07-21 Dell Products L.P. Method to deploy wireless network security with a wireless router
US20050201371A1 (en) * 2004-03-12 2005-09-15 Lucent Technologies Inc. GPRS tunneling protocol path integrity protocol
US20060029096A1 (en) * 2004-08-06 2006-02-09 Babbar Uppinder S Technology agnostic QoS support in a multi-mode environment
US7136382B1 (en) * 2000-08-25 2006-11-14 Novell, Inc. System and method for providing quality of service operations using IP addresses
US20060268818A1 (en) * 2003-03-17 2006-11-30 Xiaobao Chen Radio telecommunications apparatus and method for communcations internet data packets containing different types of data
US20060274706A1 (en) * 2003-03-17 2006-12-07 Xiaobao Chen Telecommunications apparatus and method
US7155215B1 (en) 2002-01-04 2006-12-26 Cisco Technology, Inc. System and method for upgrading service class of a connection in a wireless network
US20070127375A1 (en) * 2005-11-22 2007-06-07 Samsung Electronics Co., Ltd. Apparatus and method for classifying quality-of-service of packet in portable internet system
US20080037586A1 (en) * 2006-04-28 2008-02-14 Telefonaktiebolaget Lm Ericsson (Publ) One-To-One Relationship Between NSAPI and User-Data SAPI
US20080132268A1 (en) * 2006-12-01 2008-06-05 Cingular Wireless Ii, Llc Dynamic quality of service adaptation in packet data communications
US20080137669A1 (en) * 2006-12-12 2008-06-12 Nokia Corporation Network of nodes
US7609700B1 (en) * 2005-03-11 2009-10-27 At&T Mobility Ii Llc QoS channels for multimedia services on a general purpose operating system platform using data cards
US7788211B2 (en) * 2000-06-16 2010-08-31 Nokia Networks Oy Robust and efficient compression of list of items
US7974249B2 (en) 2006-03-01 2011-07-05 Dell Products L.P. Virtual access point for configuration of a LAN
US8638713B2 (en) 2006-12-01 2014-01-28 At&T Mobility Ii Llc Non-intrusive in-session QoS parameter modification method
US8649299B2 (en) * 2000-11-17 2014-02-11 Eimar M. Boesjes Distributed wireless online access system
US20140289800A1 (en) * 2003-09-03 2014-09-25 Cisco Technology, Inc. System and method for filtering network traffic

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2395090B (en) * 2002-10-01 2006-04-05 Ipwireless Inc Arrangement and method for session control in wireless communication network
JP4058326B2 (ja) 2002-10-17 2008-03-05 株式会社エヌ・ティ・ティ・ドコモ 無線基地局、制御装置、無線通信システム及び通信方法
FR2848052B1 (fr) * 2002-11-29 2005-03-18 Orange France Systeme et procede de selection dans un terminal pour une architecture dediee a un reseau de communication
US7383048B2 (en) 2002-12-04 2008-06-03 Nokia Corporation Transmission of data packets by a node
CN101009637B (zh) * 2006-01-26 2011-09-21 华为技术有限公司 服务质量控制方法、系统及逻辑链路管理功能设备
EP1838053A1 (fr) * 2006-03-24 2007-09-26 Orange SA Procédé et système de télécommunications
US9681336B2 (en) * 2007-06-13 2017-06-13 Qualcomm Incorporated Quality of service information configuration

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6937566B1 (en) * 1997-07-25 2005-08-30 Telefonaktiebolaget Lm Ericsson (Publ) Dynamic quality of service reservation in a mobile communications network
FI108192B (fi) * 1998-03-19 2001-11-30 Nokia Networks Oy Menetelmä ja laitteisto palvelun laadun kontrolloimiseksi matkaviestinjärjestelmässä
EP1096742A1 (fr) * 1999-10-25 2001-05-02 Lucent Technologies Inc. Réseau de communication par radio

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ETSI GSM 03.60 Standard, GPRS Service Description, Stage 2, EN 301 344 V6.3.2, pp. 18-23, 58-75, 86-91. Date: 1997.
ETSI GSM 3G TS 24.065 Technical Description, GPRS SGSN Submetwork Dependent Convergence Protocol (SNDCP), ETSI TS 124 065 V3.1.0, pp. 7-11, 17-23, 35-37. Date: 1999.

Cited By (60)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7788211B2 (en) * 2000-06-16 2010-08-31 Nokia Networks Oy Robust and efficient compression of list of items
US7136382B1 (en) * 2000-08-25 2006-11-14 Novell, Inc. System and method for providing quality of service operations using IP addresses
US9088964B2 (en) 2000-11-17 2015-07-21 Modern Medium Services Llc Distributed wireless online access system
US8923165B2 (en) 2000-11-17 2014-12-30 Modern Medium Services Llc Distributed wireless online access system
US8649299B2 (en) * 2000-11-17 2014-02-11 Eimar M. Boesjes Distributed wireless online access system
US20030081599A1 (en) * 2001-10-30 2003-05-01 Chui-Tsang Wu System and method for data transmission control
US20030083041A1 (en) * 2001-11-01 2003-05-01 Intel Corporation System and method for providing cost of quality of service levels in a wireless communication device
US7058387B2 (en) * 2001-11-01 2006-06-06 Intel Corporation System and method for providing cost of quality of service levels in a wireless communication device
US20030115515A1 (en) * 2001-12-13 2003-06-19 Curtis Chris B. Method and apparatus for testing digital channels in a wireless communication system
US6917916B2 (en) * 2001-12-13 2005-07-12 Motorola, Inc. Method and apparatus for testing digital channels in a wireless communication system
US20070049285A1 (en) * 2002-01-04 2007-03-01 Cisco Technology, Inc. System and Method for Upgrading Service Class of a Connection in a Wireless Network
US7433688B2 (en) 2002-01-04 2008-10-07 Cisco Technology, Inc. System and method for upgrading service class of a connection in a wireless network
US7155215B1 (en) 2002-01-04 2006-12-26 Cisco Technology, Inc. System and method for upgrading service class of a connection in a wireless network
US7054940B2 (en) * 2002-01-25 2006-05-30 Thomson Licensing Adaptive cost of service for communication network based on level of network congestion
US20030145098A1 (en) * 2002-01-25 2003-07-31 Litwin Louis Robert Adaptive cost of service for communication network based on level of network congestion
US20030187828A1 (en) * 2002-03-21 2003-10-02 International Business Machines Corporation Method and system for dynamically adjusting performance measurements according to provided service level
US20030187972A1 (en) * 2002-03-21 2003-10-02 International Business Machines Corporation Method and system for dynamically adjusting performance measurements according to provided service level
US6928394B2 (en) * 2002-03-21 2005-08-09 International Business Machines Corporation Method for dynamically adjusting performance measurements according to provided service level
US6931356B2 (en) * 2002-03-21 2005-08-16 International Business Machines Corporation System for dynamically adjusting performance measurements according to provided service level
US7918734B2 (en) * 2002-09-30 2011-04-05 Time Warner Cable, A Division Of Time Warner Entertainment Company, L.P. Gaming server providing on demand quality of service
US20110065500A1 (en) * 2002-09-30 2011-03-17 Kenneth Gould Gaming server providing on demand quality of service
US8475280B2 (en) * 2002-09-30 2013-07-02 Time Warner Cable Enterprises Llc Gaming server providing on demand quality of service
US20040063497A1 (en) * 2002-09-30 2004-04-01 Kenneth Gould Gaming server providing on demand quality of service
US7688859B2 (en) 2003-03-17 2010-03-30 Orange Sa Telecommunications apparatus and method
US7558240B2 (en) * 2003-03-17 2009-07-07 Orange Sa Radio telecommunications apparatus and method for communications internet data packets containing different types of data
US20060268818A1 (en) * 2003-03-17 2006-11-30 Xiaobao Chen Radio telecommunications apparatus and method for communcations internet data packets containing different types of data
US20060274706A1 (en) * 2003-03-17 2006-12-07 Xiaobao Chen Telecommunications apparatus and method
US7193979B2 (en) * 2003-07-11 2007-03-20 Nokia Corporation Method and apparatus for use by a GPRS device in responding to change in SAPI connection
US20050007981A1 (en) * 2003-07-11 2005-01-13 Nokia Corporation Method and apparatus for use by a GPRS device in responding to change in SAPI connection
US20140289800A1 (en) * 2003-09-03 2014-09-25 Cisco Technology, Inc. System and method for filtering network traffic
US9882904B2 (en) * 2003-09-03 2018-01-30 Cisco Technology, Inc. System and method for filtering network traffic
US20050053005A1 (en) * 2003-09-09 2005-03-10 Harris Corporation Mobile ad hoc network (MANET) providing connectivity enhancement features and related methods
US7142866B2 (en) 2003-09-09 2006-11-28 Harris Corporation Load leveling in mobile ad-hoc networks to support end-to-end delay reduction, QoS and energy leveling
US20050053003A1 (en) * 2003-09-09 2005-03-10 Harris Corporation Mobile ad hoc network (MANET) with quality-of-service (QoS) protocol hierarchy and related methods
US7085290B2 (en) 2003-09-09 2006-08-01 Harris Corporation Mobile ad hoc network (MANET) providing connectivity enhancement features and related methods
US20050053094A1 (en) * 2003-09-09 2005-03-10 Harris Corporation Mobile ad hoc network (MANET) providing quality-of-service (QoS) based unicast and multicast features
US7079552B2 (en) 2003-09-09 2006-07-18 Harris Corporation Mobile ad hoc network (MANET) with quality-of-service (QoS) protocol hierarchy and related methods
US7394826B2 (en) 2003-09-09 2008-07-01 Harris Corporation Mobile ad hoc network (MANET) providing quality-of-service (QoS) based unicast and multicast features
US20050054346A1 (en) * 2003-09-09 2005-03-10 Harris Corporation, Corporation Of The State Of Delaware Load leveling in mobile ad-hoc networks to support end-to-end delay reduction, QoS and energy leveling
US20050053007A1 (en) * 2003-09-09 2005-03-10 Harris Corporation Route selection in mobile ad-hoc networks based on traffic state information
US20070058535A1 (en) * 2003-09-30 2007-03-15 Guillaume Bichot Quality of service control in a wireless local area network
US8750246B2 (en) * 2003-09-30 2014-06-10 Thomson Licensing Quality of service control in a wireless local area network
WO2005041446A1 (fr) * 2003-09-30 2005-05-06 Thomson Licensing S.A. Qualite de controle de service dans un reseau local sans fil (lan)
US20050160287A1 (en) * 2004-01-16 2005-07-21 Dell Products L.P. Method to deploy wireless network security with a wireless router
US20050201371A1 (en) * 2004-03-12 2005-09-15 Lucent Technologies Inc. GPRS tunneling protocol path integrity protocol
US7414997B2 (en) * 2004-03-12 2008-08-19 Lucent Technologies Inc. GPRS tunneling protocol path integrity protocol
US8331375B2 (en) * 2004-08-06 2012-12-11 Qualcomm Incorporated Technology agnostic QoS support in a multi-mode environment
US20060029096A1 (en) * 2004-08-06 2006-02-09 Babbar Uppinder S Technology agnostic QoS support in a multi-mode environment
US8879584B2 (en) 2004-08-06 2014-11-04 Qualcomm Incorporated Technology agnostic QoS support in a multi-mode environment
US8213363B2 (en) 2005-03-11 2012-07-03 At&T Mobility Ii Llc QoS channels for multimedia services on a general purpose operating system platform using data cards
US20100017521A1 (en) * 2005-03-11 2010-01-21 Cingular Wireless Ii, Llc QoS CHANNELS FOR MULTIMEDIA SERVICES ON A GENERAL PURPOSE OPERATING SYSTEM PLATFORM USING DATA CARDS
US7609700B1 (en) * 2005-03-11 2009-10-27 At&T Mobility Ii Llc QoS channels for multimedia services on a general purpose operating system platform using data cards
US8767656B2 (en) 2005-03-11 2014-07-01 At&T Mobility Ii Llc QoS channels for multimedia services on a general purpose operating system platform using data cards
US20070127375A1 (en) * 2005-11-22 2007-06-07 Samsung Electronics Co., Ltd. Apparatus and method for classifying quality-of-service of packet in portable internet system
US8094549B2 (en) * 2005-11-22 2012-01-10 Samsung Electronics Co., Ltd Apparatus and method for classifying quality-of-service of packet in portable internet system
US7974249B2 (en) 2006-03-01 2011-07-05 Dell Products L.P. Virtual access point for configuration of a LAN
US20080037586A1 (en) * 2006-04-28 2008-02-14 Telefonaktiebolaget Lm Ericsson (Publ) One-To-One Relationship Between NSAPI and User-Data SAPI
US8638713B2 (en) 2006-12-01 2014-01-28 At&T Mobility Ii Llc Non-intrusive in-session QoS parameter modification method
US20080132268A1 (en) * 2006-12-01 2008-06-05 Cingular Wireless Ii, Llc Dynamic quality of service adaptation in packet data communications
US20080137669A1 (en) * 2006-12-12 2008-06-12 Nokia Corporation Network of nodes

Also Published As

Publication number Publication date
WO2002030056A2 (fr) 2002-04-11
AU2001283001A1 (en) 2002-04-15
WO2002030056A3 (fr) 2003-01-16

Similar Documents

Publication Publication Date Title
USH2051H1 (en) System and method for providing multiple quality of service classes
US7039025B1 (en) System and method for providing general packet radio services in a private wireless network
JP4702852B2 (ja) 異なる種類のデータを含むインターネットパケットを通信する無線電気通信装置及び方法
US6021333A (en) Method and system for transferring information within a mobile communication system
CN101502166B (zh) 在接入网关节点中提供一种数据功能
US6501741B1 (en) Method supporting the quality of service of data transmission
US7269423B2 (en) System and method for call admission for a mobile communication system
EP1123626B1 (fr) Passerelle de numero itinerant de protocole internet
US7245927B2 (en) Intelligent network interface
US7420953B2 (en) Hardware configuration, support node and method for implementing general packet radio services over GSM
US7307968B2 (en) Method and system for communicating data between a mobile communications architecture and a packet switched architecture
US6711417B1 (en) Interface using an ISH and a service manager
US8774155B2 (en) Transporting call data via a packet data network
US7068644B1 (en) Wireless access gateway to packet switched network
US20050201336A1 (en) System and method for providing codec information in a mobile communication network
WO2000008803A9 (fr) Architecture sans fil autoconfigurable prenant acceptant des paquets de donnees et des services ip phonie/multimedia
JP2002528975A (ja) デジタルテレコミュニケーションシステム
JP2003526997A (ja) サービス情報伝送方法及び無線システム
US8953588B2 (en) Mobile network with packet data network backhaul
US6904034B2 (en) Method and system for communicating data between a mobile communications architecture and a packet switched architecture, each utilizing a different mode of communication
US20020131447A1 (en) System and method for wireless packet data content switch
US7242944B1 (en) Method and system for dynamically re-homing a base transceiver station
US20050232235A1 (en) Method and system for providing an interface between switching equipment and 2G wireless interworking function
WO2001060091A1 (fr) Procede et systeme d'interfonctionnement de messages vocaux de signalisation entre des reseaux a commutation de circuit et des reseaux de commutation par paquets
WO2001060094A1 (fr) Procede et systeme d'interfonctionnement de reseaux a commutation de circuit et de reseaux de commutation par paquets

Legal Events

Date Code Title Description
AS Assignment

Owner name: OPUSWAVE NETWORKS, INC., COLORADO

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ZHU, YINJUN;MANSFIELD, CARL;CARLTON, ALAN;AND OTHERS;REEL/FRAME:011829/0700;SIGNING DATES FROM 20010111 TO 20010504

STCF Information on status: patent grant

Free format text: PATENTED CASE