HK1143678A - Quality of service information configuration - Google Patents

Description

Quality of service information configuration

Cross-referencing

This application claims priority to U.S. application No.60/943,670 entitled "QoS IN UMB/CANSYSTEMS" filed on 13.6.2007. The entire contents of the aforementioned application are hereby incorporated by reference.

Technical Field

The following description relates generally to the field of wireless communications, and more particularly to configuring and maintaining quality of service information.

Background

Wireless communication systems are widely deployed to provide various types of communication content such as voice, data, and so on. A typical wireless communication system may be a multiple-access system capable of supporting communication with multiple users by sharing the available system resources (e.g., bandwidth, transmit power). Examples of such multiple-access systems may include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, and the like.

Generally, wireless multiple-access communication systems are capable of supporting communication for multiple mobile devices simultaneously. Each mobile device may communicate with one or more base stations via transmissions on forward and reverse links. The forward link (or downlink) refers to the communication link from base stations to mobile devices, and the reverse link (or uplink) refers to the communication link from mobile devices to base stations. Moreover, communications between mobile devices and base stations can be established over single-input single-output (SISO) systems, multiple-input single-output (MISO) systems, multiple-input multiple-output (MIMO) systems, and so forth.

MIMO systems typically employ multiple (N)_T) Transmitting antenna and a plurality of (N)_R) The receive antennas are used for data transmission. May be composed of N_TA transmitting antenna and N_RMIMO channel decomposition into N_SIndividual channels, which may also be referred to as spatial channels, where N_S≤{N_T，N_R}。N_SEach of the individual channels corresponds to a dimension. Furthermore, MIMO systems may provide improved performance (e.g., increased spectral efficiency, higher throughput, and/or greater reliability) if the additional dimensionalities created by the multiple transmit and receive antennas are utilized.

MIMO systems may support various duplexing techniques to divide forward and reverse link communications over a common physical medium. For example, a Frequency Division Duplex (FDD) system may utilize different frequency regions for forward link and reverse link communications. Further, in a Time Division Duplex (TDD) system, forward link and reverse link communications may employ a common frequency region. However, conventional techniques may provide only limited or no feedback related to channel information.

Disclosure of Invention

The following presents a simplified summary of one or more embodiments in order to provide a basic understanding of such embodiments. This summary is not an extensive overview of all contemplated embodiments, and is intended to neither identify key or critical elements of all embodiments nor delineate the scope of any or all embodiments. Its sole purpose is to present some concepts of one or more embodiments in a simplified form as a prelude to the more detailed description that is presented later.

In accordance with one or more embodiments and corresponding disclosure thereof, various aspects are described in connection with a method for initiating quality of service from a network entity. The method may include establishing a traffic plane function with a network and performing a quality of service configuration with the network by using the traffic plane function.

According to another aspect, there may be a wireless communication apparatus comprising: the setting-up device establishes the service plane function with the network; and a setter for performing quality of service configuration with the network by using the service plane function.

According to another aspect, there may be a wireless communication apparatus. The apparatus may include means for establishing a traffic plane function with a network. The apparatus may also include means for performing quality of service configuration with the network using the traffic plane function.

Further, there may be aspects related to a machine-readable medium having stored thereon machine-executable instructions for establishing traffic plane functions with a network and performing quality of service configuration with the network using the traffic plane functions.

Further, there may be aspects related to a wireless communication system including an apparatus comprising a processor. The processor may be configured to establish a traffic plane function with a network and perform a quality of service configuration with the network using the traffic plane function.

According to one aspect, there may be a method for initiating quality of service from a network, the method comprising establishing a traffic plane function directly with a network entity, and performing quality of service configuration with the network entity by using the traffic plane function.

Another aspect can facilitate use of a wireless communication device. The apparatus may include: the constructor directly establishes a service plane function with a network entity; and a manager performing quality of service configuration with the network entity by using the service plane function.

In one aspect, there may be a wireless communications apparatus comprising: a module for establishing service plane functions directly with a network entity; and means for performing quality of service configuration with the network entity using the traffic plane function.

Further, an aspect may relate to a machine-readable medium. The machine-readable medium may have stored thereon machine-executable instructions for establishing traffic plane functionality directly with a network entity. There may also be instructions for performing quality of service configuration with the network entity using the traffic plane function.

In another aspect, there may be a wireless communication system having an apparatus comprising: a processor for establishing a service plane function directly with a network entity and performing a quality of service configuration with the network entity by using the service plane function.

To the accomplishment of the foregoing and related ends, the one or more embodiments comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative aspects of the one or more embodiments. These aspects are indicative, however, of but a few of the various ways in which the principles of various embodiments may be employed and the described embodiments are intended to include all such aspects and their equivalents.

Drawings

Fig. 1 is an illustration of a wireless communication system in accordance with various aspects set forth herein.

Fig. 2 is an illustration of a representative system that facilitates communicating utilizing quality of service information in accordance with various aspects presented herein.

Fig. 3 is an illustration of a representative system that facilitates initiating communication of quality of service information in accordance with various aspects presented herein.

Fig. 4 is an illustration of a representative system that facilitates employing a particular network configuration for communicating using quality of service information in accordance with various aspects presented herein.

Fig. 5 is an illustration of a representative system that facilitates employing a particular network entity for communicating using quality of service information in accordance with various aspects presented herein.

Fig. 6 is an illustration of a representative system that facilitates employing a particular network entity for communicating using quality of service information in accordance with various aspects presented herein.

Fig. 7 is an illustration of a representative network configuration in accordance with various aspects set forth herein.

Fig. 8 is an illustration of a representative methodology for utilizing quality of service information for wireless communication in accordance with various aspects presented herein.

Fig. 9 is an illustration of a representative methodology for processing a plurality of protocol data units in accordance with various aspects set forth herein.

Fig. 10 is an illustration of a representative methodology for transmitting a protocol data unit in accordance with various aspects presented herein.

Fig. 11 is an illustration of an example mobile device that facilitates utilizing quality of service information in accordance with various aspects presented herein.

Fig. 12 is an illustration of an example system that facilitates utilizing network entity-initiated quality of service information in accordance with various aspects presented herein.

Fig. 13 is an illustration of an example wireless network environment initiated by a network configuration that can be employed in conjunction with the various systems and methods described herein.

Fig. 14 is an illustration of an example system that facilitates utilizing network entity-initiated quality of service information in accordance with various aspects set forth herein.

Fig. 15 is an illustration of an example system that facilitates employing network configuration-initiated quality of service information in accordance with various aspects set forth herein.

Detailed Description

The techniques described herein may be used for various wireless communication systems, such as code division multipleSite (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), single carrier FDMA (SC-FDMA), and other systems. The terms "system" and "network" are often used interchangeably. A CDMA system may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), CDMA2000, etc. UTRA includes wideband CDMA (W-CDMA) and other variants of CDMA. CDMA2000 covers the transitional standard (IS) -2000, IS-95 and IS-856 standards. TDMA systems may implement wireless technologies such as global system for mobile communications (GSM). OFDMA systems may implement methods such as evolved Universal terrestrial radio Access (evolved UTRA or E-UTRA), Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE)802.11(Wi-Fi), IEEE 802.16(WiMAX), IEEE 802.20, Flash-And so on. Universal Terrestrial Radio Access (UTRA) and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) is a upcoming release of UMTS that uses E-UTRA, which employs OFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTE, and GSM are described in documents of the organization entitled "third Generation partnership project" (3 GPP). CDMA2000 and UMB are described in a document entitled "third generation partnership project 2" (3GPP2) organization.

Various embodiments are now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more embodiments. It may be evident, however, that such embodiment(s) may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing one or more embodiments.

As used in this application, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal).

Moreover, various embodiments are described herein in connection with a mobile device. A mobile device can also be called a system, subscriber unit, subscriber station, mobile, remote station, remote terminal, access terminal, user terminal, wireless communication device, user agent, user device, or User Equipment (UE). The mobile device may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having wireless connection capability, a computing device, or other processing device connected to a wireless modem. Moreover, various embodiments are described herein in connection with a base station. A base station can be utilized for communicating with mobile device(s) and can also be referred to as an access point, a node B, or some other terminology.

Moreover, various aspects or features described herein can be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD), etc.), smart cards, and flash memory devices (e.g., EPROM, card, stick, key drive, etc.). In addition, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data.

Referring now to fig. 1, a wireless communication system 100 is illustrated in accordance with various embodiments presented herein. System 100 comprises a base station 102 that can include multiple antenna groups. For example, one antenna group can include antennas 104 and 106, another group can include antennas 108 and 110, and an additional group can include antennas 112 and 114. Two antennas are shown for each antenna group; however, more or fewer antennas may be utilized for each group. Base station 102 can additionally comprise a transmitter chain and a receiver chain, each of which can in turn comprise a plurality of components associated with signal transmission and reception (e.g., processors, modulators, multiplexers, demodulators, demultiplexers, antennas, etc.), as will be appreciated by one skilled in the art.

Base station 102 can communicate with one or more mobile devices (e.g., mobile device 116 and mobile device 122); it should be noted, however, that base station 102 can communicate with substantially any number of mobile devices similar to mobile devices 116 and 122. For example, mobile devices 116 and 122 can be cellular phones, smart phones, laptops, handheld communication devices, handheld computing devices, satellite radios, global positioning systems, PDAs, and/or any other suitable device for communicating over wireless communication system 100. As depicted, mobile device 116 is in communication with antennas 112 and 114, where antennas 112 and 114 transmit information to mobile device 116 over a forward link 118 and receive information from mobile device 116 over a reverse link 120. In addition, mobile device 122 is in communication with antennas 104 and 106, where antennas 104 and 106 transmit information to mobile device 122 over a forward link 124 and receive information from mobile device 122 over a reverse link 126. In a Frequency Division Duplex (FDD) system, forward link 118 can utilize a different frequency band than that used by reverse link 120, and forward link 124 can employ a different frequency band than that employed by reverse link 126, for example. Further, in a Time Division Duplex (TDD) system, forward link 118 and reverse link 120 can utilize a common frequency band and forward link 124 and reverse link 126 can utilize a common frequency band.

Antenna groups and/or the areas in which they are designated to communicate can be referred to as sectors of base station 102. For example, multiple antennas can be utilized to communicate to mobile devices in a sector of the areas covered by base station 102. In communication over forward links 118 and 124, the transmitting antennas of base station 102 can utilize beamforming to improve signal-to-noise ratio of forward links 118 and 124 for mobile devices 116 and 122. Moreover, when base station 102 utilizes beamforming to transmit to mobile devices 116 and 122 scattered randomly through an associated coverage, mobile devices in neighboring cells can be subject to less interference as compared to a base station transmitting through a single antenna to all its mobile devices.

Referring now to fig. 2, an example system 200 for configuring quality of service (QoS) for use in data communications is disclosed. The use of QoS information allows communication resources to be conserved-in particular resources may be allocated for cellular communications. A particular network entity may initiate QoS information configuration, such as mobile device 1116 of fig. 1 or base station 102 of fig. 1. However, the network may also configure QoS information for network entities (e.g., access terminals).

The network configuration 202 may organize QoS information regarding interactions with the network entities 204. The composer 206 may establish a traffic plane function with the network entity 204. The service plane function may represent an access gateway that may aggregate usage information and report the aggregated results to the usage function. The manager 208 may perform QoS configuration with the network entity 204 by using traffic plane functions. There may be a policy decision entity (e.g., maintained in the composer 206, manager 208, a separate entity, etc.) used by the network configuration 202, wherein the policy decision entity is capable of providing dynamic policies related to QoS and charging to the access gateway, enabling the access gateway to establish internet protocol and access network resources of the network entities related to these policy decisions. Further, the network configuration 202 may also include a static configuration entity (e.g., maintained in the composer 206, the manager 208, a separate entity, etc.), wherein the static configuration entity may provide static policy or configuration information related to QoS and charging to the network entity 204.

Instead, the network entity 204 may utilize the network configuration 202 to configure or obtain authorization for QoS information. An establisher 210 may be used that establishes traffic plane functionality with the network (e.g., network configuration 202). The setter 212 may perform quality of service configuration with the network by using a traffic plane function. A network entity (e.g., an access terminal) may initiate QoS establishment to an access gateway, which may send information to a policy decision entity within network configuration 202 for authorization. The policy decision entity may provide an authorization decision back to the access gateway and may also provide policy enforcement rules related to authorization.

In both the network entity initiated and network configuration initiated scenarios, an efficient QoS architecture may be provided (e.g., packet filters are established in the access network and Differentiated Services Code Point (DSCP) marking is used to provide QoS in the backhaul). Furthermore, there may be additional new QoS attributes from home authentication, authorization and accounting (HAAA) to inter-user priority (e.g., user class) of the access network for admission control and QoS handling. In addition, at least one mechanism may be added as to how the access network marks the DSCP on the reverse link and how the access gateway marks the DSCP on the forward link. Further, service-based bearer control (SBBC) support may be provided to the access network (e.g., how and what SBBC parameters to transmit to the access network, etc.). This support can be used to address issues regarding how network entity 204-initiated (e.g., access terminal-initiated) QoS and network configuration 202-initiated QoS work with SBBC/Policy and Change Control (PCC).

In addition, other functions related to QoS information may be used. The token may be used to match rules maintained at a network entity, such as an evolved node b (enb), with actually received rules (e.g., the token goes from the network entity 204 to application functions and policy decision functions). This may replace packet filter matching. In addition, the interoperability specification (IOS) signaling may be used to carry policy information instead of diameter or radius. There may also be multiple Internet Protocols (IPs) addressed associated with one policy session between the access gateway and the policy decision entity. Within the access network, a QoS reserved for a certain application is identified using a reserved identity. Dividing the save identification space into two parts may occur: one part for network entity initiation and one part for network configuration initiation. Information may be provided to network entity 204 so that network entity 204 can know whether network entity-initiated QoS or network configuration-initiated QoS is used for each application.

Referring now to fig. 3, an example system 300 for initiating QoS communications from a network and/or network entity is disclosed. An access terminal 302 (e.g., an example network entity) may communicate with an application function 306 through a network 304 and an access gateway 310. The network may communicate with an application function 306, a policy decision point 308, and an access gateway 310.

According to push mode, access terminal 302 may communicate with application function 306 through network 304 and access gateway 310. Application function 306 may authorize QoS and communicate the QoS to policy decision point 308 for service-based authorization. Policy decision point 308 may communicate the policy decision to access gateway 310. Additional bearer control may be performed between access terminal 302, network 304, and access gateway 310, if desired. Access gateway 310 may compare the authorized QoS to the requested IP level for QoS. The comparison results may be used to facilitate QoS communications. The access gateway may provide the policy decision received from policy decision point 308 to network 304 for enforcement. Multiple entities in network 304 may be included in communication with access terminal 302. A synchronization mechanism may be used to update policy and enforcement information on multiple entities within network 304. The synchronization mechanism may also include interaction with the access terminal 302. It is to be appreciated that system 300 can operate without network 304 such that direct communication is effectuated from access terminal 302 (e.g., in an access terminal initiated configuration).

In another embodiment, access terminal 302 (or network 304 in the case of network initiation) may exchange information with application function 306. Application function 306 may authorize QoS parameters and communicate these parameters to policy decision point 308, where there may be locally IP-authorized QoS parameters (e.g., where policy decision point 308 collects management policies). Information may be bound between access terminal 302 and access gateway 310 and between access gateway 310 and policy decision point 308. The local IP authorized QoS parameters may become IP level authorized QoS parameters for access gateway 310. Access gateway 310 may compare the authorized QoS to the requested IP level for QoS. The comparison results may be used to facilitate QoS communications.

According to one embodiment, a token may be communicated between the access terminal 302 and the application function 306, and the application function communicates the token to the policy decision point 308. Policy decision point 308 may then communicate the token with the QoS rules to access gateway 310 and network 304. Access terminal 302 may then communicate the same token to network 304 when requesting QoS. Thus, the network 304 may know that the access terminal 302 is requesting information related to the content indicated by the application function 306. An IOS may exist between network 304 and access gateway 310 or between multiple network entities within network 304. The stored identifier space may be used between access terminal 302 and network 304 (e.g., an access network) and may be divided into two spaces: one for access terminal initiated QoS and one for network initiated QoS.

The access terminal 302 (e.g., mobile device) and the application function 306 can negotiate information related to the application. The application function 306 may communicate the service information to the policy decision point 308 for authorization. The policy decision point may authorize the service and derive policy rules based on the authorized service information. Policy decision point 308 may communicate the policy rules to access gateway 310 and access gateway 310 may redistribute the rules to network 304. Access gateway 310 or the network may initiate QoS establishment based on the received rules.

In a pull mode (pull mode) embodiment, the access terminal 302 may establish a basic QoS with the network 304 based on some pre-configured information or application that the access terminal 302 intends to start. Establishment may trigger access gateway 302 to request authorization from policy decision point 308. Once QoS is available or in parallel with QoS establishment, access terminal 302 and application function 306 can negotiate application information. The application function may communicate the service information to the policy decision point 308 for authorization. The policy decision point 308 may authorize the service and derive the associated policy rules. Because access gateway 310 can request QoS for the service in advance, policy decision point 308 can correlate the rules with the previous authorization and send an update to access gateway 310. The access gateway may provide the policy decision received from policy decision point 308 to network 304 for enforcement. Multiple entities in network 304 may be included in communication with access terminal 302. A synchronization mechanism may be used to update policy and enforcement information on multiple entities within network 304. The synchronization mechanism may also include interaction with the access terminal 302. The aspects disclosed in fig. 3 may be applied to other aspects disclosed herein (e.g., the network configuration 202 of fig. 2 and/or the network entity 204 of fig. 2).

Referring now to fig. 4, an example system 400 for configuring quality of service for use in data communications using a specific network configuration 202 is disclosed. Thus, system 400 may represent a network configuration 202 initiated scenario. A composer 206 may be used which establishes traffic plane functionality directly with the network entity. Further, the manager 208 may perform QoS configuration with the network entity 204 by using the traffic plane function.

Various other modules may be used to facilitate functionality and improve QoS operations. The network configuration may use a collector 402 that collects QoS information from the access gateways, which may obtain the QoS information from the policy change rule function. This may be done before the call is configured, where the call is not considered allowed.

Further, a container 404 can be employed that retains QoS information prior to initiating a communication link, configuring the retained quality of service information. It is generally considered that QoS information cannot be configured before a link is established. However, the policies may be configured and exchanged between different network entities (e.g., network entity 204), network configuration 202, etc., that are capable of allowing information to be shared and used for QoS information at the time of the call.

According to one embodiment, the amount of QoS information may be preserved prior to establishing a call. A holder 406 may be used to hold the pieces of QoS information, typically prior to setting up the call. Network entity 204 may use a portion of the saved QoS information fragment. The network configuration 202 may then release QoS information that is not used by the network entity 204. Generally, the holder 406 holds larger fragments than the network entity 204 is able to use. This may be considered a guarantee that the call can start because sufficient QoS information is maintained for the network entity 204, which may allow for faster calls because the QoS information is already available.

Because the network configuration 202 may have a different policy than the at least one network entity 204, different outputs may be produced from similar requests. Thus, an advancer 408 can be implemented that uses an update process to synchronize at least one policy between a network entity and a network — thus, similar outputs can be produced from a common command. The network entity 204 may use the receiver 410 for communication and the processor 412 to facilitate operations. Using system 400 can result in the use of partial session information based policy authorization for improved (e.g., optimized) call flow.

By using QoS configurations as disclosed herein, several elements of functionality may be implemented. There may be pre-authorization from the policy decision point to allow QoS preservation prior to call setup (e.g., the QoS portion preserved prior to implementing the setup process for the call). Furthermore, through the context update procedure, policy synchronization may be performed between network entities (e.g., pushing a complete rule set from the access gateway to the network at a time to avoid a contention situation). Further, subscription-based policy authorization may be used with policy updates and latest bindings to allow improved call flow.

Referring now to fig. 5, an example system 500 is disclosed for configuring quality of service for use in data communications through the use of a particular network entity 204. The network entity 204 may provide information to the network configuration 202 to facilitate use of the QoS information. A network entity may use receiver 502 for communication and processor 504 for analyzing data.

The network entity 204 may use an establisher 210 that establishes traffic plane functionality with the network (e.g., the network configuration 204). The setter 212 can perform QoS configuration with the network by using the service plane function. Different functions may enable various features to be used for QoS information usage. According to one embodiment, configuring the traffic plane functionality is accomplished by using subscription policies, policy updates, and late bindings. The recorder 506 may save the QoS information prior to initiating the communication link; the saved QoS information is typically configured by the setter 212.

Similar to what is described in the network entity initiated implementation (e.g., what is shown in fig. 4), different policies may lead to different results, which may be undesirable. The equalizer 506 may address the undesirable effect by using an update procedure to synchronize at least one policy between the network entity and the network. In conventional communication systems, temporary identifications may be provided to entities. However, if the same temporary identity is not available in all involved entities, there may be a correction problem. An identifier 508 may be used that provides a permanent identification of the network entity to the network. Thus, a permanent Network Address Identifier (NAI) may be provided from the HAAA (e.g., HAAA server) to the access gateway for use by the access gateway in communicating with the policy decision point, which also receives the same permanent identification from the HAAA for correction.

Referring now to fig. 6, an example system 500 is disclosed for communicating information as part of a network, such as over an Ultra Mobile Broadband (UMB) radio access technology. The eBS 602 (evolved base station, such as base station 102 of FIG. 1) can interface with the DAP (data arrival point) and/or SRNC (signal radio network controller) 604, wherein the SRNC604 maintains a session reference. The DAP and/or SRNC604 can communicate with an AGW 606 (an access gateway, such as access gateway 310 of FIG. 3). Through the AGW 606, a number of entities can utilize the AGW 606 to communicate with the eBS 602, thereby providing Internet protocol conductivity to the network to the user site. The AGW 606 may interface with an AAA 608 (authentication, authorization, and accounting functions), wherein the AAA 608 may provide authentication, authorization, and accounting functions for access terminal usage of network resources. Further, the AGW 606 can communicate with a HA 610 (home agent), wherein the HA 610 provides mobility functionality. The LMA 612 (local mobility anchor) may connect directly with the AGW 606 or connect with the AGW 606 by communicating with the PCRF 614 (policy and change rules function), where the PCRF 614 provides the criteria used by the AGW 606 operation. The LMA 612 may serve as an anchor for the mobile terminal and manage reachable states of the mobile terminal.

Referring to fig. 7-10, methodologies relating to the communication of QoS information are illustrated. While, for purposes of simplicity of explanation, the methodologies are shown and described as a series of acts, it is to be understood and appreciated that the methodologies are not limited by the order of acts, as some acts may, in accordance with one or more embodiments, occur in different orders and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a methodology in accordance with one or more embodiments.

Referring now to fig. 7, an example methodology 700 for utilizing QoS information in network entity initiated provisioning is disclosed. At event 702, a traffic plane function may be established with the network. The QoS information may be preserved prior to initiating the communication link at event 704, which may be facilitated by pre-authorization of the policy.

With the traffic plane functionality established, QoS configuration may be performed with the network by using the traffic plane functionality through act 706. Accordingly, the saved QoS information is configured (e.g., by saving the QoS information via act 706). At block 708, an update procedure can be used to synchronize at least one policy between the network entity and the network. According to one embodiment, configuring the traffic plane functionality is accomplished by using subscription policies, policy updates, and late bindings. Providing the network with a permanent identification of the network entity may also be performed by act 710, which act 710 may occur when or prior to establishing the traffic plane functionality at event 702.

Referring now to fig. 8, an example methodology 800 is disclosed for utilizing QoS information in network entity initiated provisioning. At act 802, a traffic plane function may be established with a network entity. With the collected traffic planes, collecting quality of service information from the access gateway may occur at act 804. According to one embodiment, the access gateway obtains quality of service information from a policy change rule function. At event 806, QoS configuration can also be performed with the network entity using the traffic plane function. Further, QoS information may be saved prior to initiating the communication link, wherein the saved QoS information is configured.

At act 808, the QoS information segment may be saved. A request may then be sent to an entity, where the entity may provide a response. The entity may provide the response collected at act 810 and a test 812 may be made to determine whether the entity specifies a QoS information portion. Typically, the entity wishes to use a portion of the saved QoS and notify the network of such a desire, so that the portion can be specified at event 814. There may also be a need for more QoS than the saved QoS, which may be updated based on actual requests using the method 800. However, it is possible that the entity does not make a designation, so the network can determine how much QoS information to save for use. This determination may be made by using artificial intelligence techniques.

Artificial intelligence techniques can employ one of a number of methods to learn from data and then make inferences and/or make decisions related to dynamically storing information between a number of storage units (e.g., Hidden Markov Models (HMMs) and related prototypical dependency models, more general probabilistic graphical models such as bayesian networks, e.g., created by structure search using bayesian model calculations or approximations, linear classifiers such as Support Vector Machines (SVMs), non-linear classifiers such as methods known as "neural network" methodologies, fuzzy logic methodologies, and other methods that perform data fusion, etc.), thereby implementing various automated aspects described herein. In addition, these techniques may also include methods for capturing logical relationships, such as theorem proving or more heuristic rule-based expert systems. Artificial intelligence techniques can be used to perform the determinations disclosed herein. Based on saving the portion of the fragment that is designated for use (e.g., requested by the entity, determined, etc.), the remaining portion may be released at act 816. Alternatively, if the required QoS is greater than the saved segments, additional resources are provided at act 816. At event 818, an update procedure can be used to synchronize at least one policy between the network entity and the network.

Referring now to fig. 9, an example method 900 for network entity initiated QoS implementation is disclosed. At event 902, a preparation activity related to the quality of service information can be performed. Initially, access authentication and authorization may be performed. With proper authentication and/or authorization, the application can start.

At block 904, a request to use QoS information associated with an application may be processed. The application sends the QoS request to a network entity, which may forward the request throughout the network. The network may authorize the QoS request, modify the request, make suggestions related to the request, and the like.

Responses related to the request to use the QoS information may be collected at act 906. In addition to sending QoS responses, the network may communicate configuration data, suggestions to network entities, etc., where the configuration data may be specific to the network. The network entity may process the response and configuration data and forward the information to the application. The application may be located on a network entity, located in another location, etc.

With the appropriate response, the application may be activated via event 908. Further, there may be an Open (ON) request, where the open request is used in the configuration related to QoS information through act 910. The application may send an open request to the access terminal, where the access terminal sends a save open request to the access network, which may then accept. The access terminal may then send a QoS open to the application. A signaling trigger may occur via event 912. The application triggers a Session Initiation Protocol (SIP) or a non-SIP to the application server. If it is determined that the signaling is complete, data may flow.

Referring now to fig. 10, an example methodology 1000 for network-initiated QoS establishment is disclosed. At event 1002, a preparation activity may be performed. This may include when the Access Terminal (AT) performs successful access authentication and authorization. Further, there can be authentication and authorization procedures, and the QoS user profile can be sent to a Signaling Radio Network Controller (SRNC). The SRNC sends the QoS user profile as session information to the eBS, which is represented by action 1004. At act 1006, a tunnel between the DAP and the AGW can be established. An IP address may also be assigned. Because SBBC is supported, the AGW establishes paths with the vprff and hPCRF. Static policies can be sent from the vprff and hPCRF to the AGW, and the AGW sends it to the SRNC.

An initial activation activity may occur via block 1008. The application may be activated. The application may also send the activated application to the AT. The application may trigger SIP or non-SIP signaling to the application server. In case of being triggered by application signaling, the application server sends an SBBC push (push) to the vpre/hPCRF, which sends the SBBC push to the AGW containing the session QoS. In addition, the AGW may push the SBBC to the AN/DAP.

At event 1010, network authorization may occur. The AN may authorize QoS based on the QoS user profile. The AN may send a configuration request to the AT, the configuration request including a save KKQoS request and TFT. The AT may send a configuration response to the AN. The AN may also send a save open request to the AT, the request including the granted QoS. The AT may also send ForReservationAck and/or RevReservationAccept to the AN, and the AT sends a QoS ON to the application. At act 1012, a notification action can occur such that the DAP notifies the SRNC of the session QoS, which can be performed in parallel with the AN authorizing QoS based on the QoS user profile. The DAP sends the reconfigured session to the AT. In addition, the AT can notify all active set members to fetch a new session from the SRNC.

It is to be appreciated that, in accordance with one or more aspects described herein, inferences can be made regarding whether QoS communication should be employed, determining wake-up period parameters, and/or the like. As used herein, the term to "infer" or "inference" refers generally to the process of reasoning about or inferring states of the system, environment, and/or user from a set of observations as captured via events and/or data. Inference can be employed to identify a specific context or action, or can generate a state probability distribution. The inference can be probabilistic-that is, the computation of a probability distribution over states of interest based on a consideration of data and events. Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data. The inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources.

According to an example, one or more methods presented above can include making inferences pertaining to using QoS information in a network setting. By way of another example, inferences can be made regarding: the plurality of physical frames are selected according to the wake-up period parameters based on the target application, desired power savings, and the like. It will be appreciated that the foregoing examples are exemplary in nature and are not intended to limit the number of inferences that can be made or the manner in which such inferences are made in conjunction with the various embodiments and/or methods described herein.

Fig. 11 is an illustration of a mobile device 1100 that facilitates employing QoS information, wherein the mobile device 1100 can act as a network entity (e.g., an access terminal). Mobile device 1100 comprises a receiver 1102 that receives a signal from, for instance, a receive antenna (not shown), and performs typical actions thereon (e.g., filters, amplifies, downconverts, etc.) the received signal and digitizes the conditioned signal to obtain samples. Receiver 1102 can be, for example, an MMSE receiver, and can comprise a demodulator 1104 that can demodulate received symbols and provide them to a processor 1106 for channel estimation. Processor 1106 can be a processor dedicated to analyzing information received by receiver 1102 and/or generating information for transmission by a transmitter 1116, a processor that controls one or more components of mobile device 1100, and/or a processor that both analyzes information received by receiver 1102, generates information for transmission by transmitter 1116, and controls one or more components of mobile device 1100.

Mobile device 1100 can additionally comprise memory 1108 that is operatively coupled to processor 1106 and that can store data to be transmitted, received data, information related to available channels, data associated with analyzed signal and/or interference strength, information related to an assigned channel, power, rate, or the like, and any other suitable information for estimating a channel and communicating via the channel. Memory 1108 can also store protocols and/or algorithms associated with estimating and/or utilizing a channel (e.g., performance based, capacity based, etc.).

It will be appreciated that the data store (e.g., memory 1108) described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. By way of example, and not limitation, nonvolatile memory can include Read Only Memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable PROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM), which acts as external cache memory. By way of example and not limitation, RAM may take many forms, such as Synchronous RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct bus RAM (DRRAM). The memory 1108 of the subject systems and methods is intended to comprise, without being limited to, these and any other suitable types of memory.

The processor 1102 may also be operatively coupled to an establisher 1110 and/or a setter 1112. The establisher 1110 may establish a traffic plane function with the network and the establisher 1112 may perform QoS configuration with the network by using the traffic plane function. Mobile device 1100 also comprises a modulator 1114 and a transmitter 1116 that transmits signals (e.g., a base station, a differential CQI) to, for instance, another mobile device, etc. Although depicted as being separate from the processor 1106, it is to be appreciated that the establisher 1110 and/or the setter 1112 may be part of the processor 1106 or processors (not shown).

Fig. 12 is an illustration of a system 1200 that facilitates communicating network-initiated QoS information, wherein the system 1200 can represent a network configuration. System 1200 includes a base station 1202 (e.g., an access point) having a receiver 1210 and a transmitter 1222, wherein receiver 1210 receives signals from one or more mobile devices 1204 via a plurality of receive antennas 1206 and transmitter 1222 transmits to the one or more mobile devices 1204 via a plurality of transmit antennas 1208. Receiver 1210 can receive information from receive antennas 1206 and is operatively associated with a demodulator 1212 that demodulates received information. Demodulated symbols can be analyzed by a processor 1214 that is similar to the one described with reference to fig. 11, and processor 1214 can be coupled to a memory 1216, wherein memory 1216 stores information related to estimating signal (e.g., pilot) strength and/or interference strength, data to be transmitted to or received from mobile device 1204 (or a disparate base station (not shown)), and/or any other suitable information related to performing the various acts and functions presented herein.

Processor 1214 is also coupled to composer 1218 and/or manager 1220. Composer 1218 may establish a traffic plane function with the network entity. The manager 1220 may perform QoS configuration with a network entity by using a traffic plane function. Although depicted as being separate from the processor 1214, it is to be appreciated that the composer 1218 and/or the manager 1220 can be part of the processor 1214 or a number of processors (not shown).

Fig. 13 illustrates an exemplary wireless communication system 1300. The wireless communication system 1300 depicts one base station 1310 and one mobile device 1350 for sake of brevity. However, it is to be appreciated that system 1300 can include more than one base station and/or more than one mobile device, wherein additional base stations and/or mobile devices can be substantially similar or different from example base station 1310 and mobile device 1350 described below. Moreover, it is to be appreciated that base station 1310 and/or mobile device 1350 can employ the systems (fig. 1-6 and 11-12) and/or methods (fig. 7-10) described herein to facilitate wireless communication between base station 1310 and mobile device 1350.

At base station 1310, traffic data for a number of data streams is provided from a data source 1312 to a Transmit (TX) data processor 1314. According to an example, each data stream can be transmitted over a respective antenna. TX data processor 1314 can format, code, and interleave each traffic data stream based on a particular coding scheme selected for that data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot data using Orthogonal Frequency Division Multiplexing (OFDM) techniques. Additionally or alternatively, the pilot symbols may be Frequency Division Multiplexed (FDM), Time Division Multiplexed (TDM), or Code Division Multiplexed (CDM). The pilot data is typically a known data pattern that is processed in a known manner and can be used at mobile device 1350 to estimate channel response. The multiplexed pilot and coded data for each data stream can be modulated (e.g., symbol mapped) based on a particular modulation scheme (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM), etc.) selected for that data stream to generate modulation symbols. The data rate, coding, and modulation for each data stream can be determined by instructions performed or provided by processor 1330.

The modulation symbols for the data streams can be provided to a TX MIMO processor 1320, which can further process the modulation symbols (e.g., for OFDM). TX MIMO processor 1320 then maps N_TA stream of modulation symbols is provided to N_TA transmitter (TMTR)1322a through 1322 t. In various embodiments, TX MIMO processor 1320 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

Each transmitter 1322 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. In addition, from N_TN transmitted by antennas 1324a through 1324t from transmitters 1322a through 1322t, respectively_TA modulated signal.

At mobile device 1350, by N_RThe transmitted modulated signals are received by antennas 1352a through 1352r and the received signal from each antenna 1352 is provided to a respective receiver (RCVR)1354a through 1354 r. Each receiver 1354 conditions (e.g., filters, amplifies, and downconverts) a respective signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding "received" symbol stream.

RX data processor 1360 can receive and process data from N based on a particular receiver processing technique_RN of a receiver 1354_RA stream of received symbols to provide N_TA stream of "detected" symbols. RX data processor 1360 can demodulate, deinterleave, and decode each detected symbol stream to recover the traffic data for the data stream. The processing by RX data processor 1360 is complementary to that performed by TX MIMO processor 1320 and TX data processor 1314 at base station 1310.

A processor 1370 can periodically determine which precoding matrix to utilize as discussed above. Further, processor 1370 can formulate a reverse link message comprising a matrix index portion and a rank value portion.

The reverse link message may comprise various types of information regarding the communication link and/or the received data stream. The reverse link message may be processed by a TX data processor 1338, modulated by a modulator 1380, conditioned by transmitters 1354a through 1354r, and transmitted back to base station 1310, where TX data processor 1338 also receives traffic data for a number of data streams from a data source 1336.

At base station 1310, the modulated signals from mobile device 1350 are received by antennas 1324, conditioned by receivers 1322, demodulated by a demodulator 1340, and processed by a RX data processor 1342 to extract the reverse link message transmitted by mobile device 1350. Further, processor 1330 can process the parsed message to determine which precoding matrix to use for determining the beamforming weights.

Processors 1330 and 1370 can direct (e.g., control, coordinate, manage, etc.) operation at base station 1310 and mobile device 1350, respectively. Respective processors 1330 and 1370 can be associated with memories 1332 and 1372, wherein memories 1332 and 1372 store program codes and data. Processors 1330 and 1370 can also perform computations to derive frequency and impulse response estimates for the uplink and downlink, respectively.

It is to be understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the processing unit may be implemented within one or more of the following electronic units: an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a processor, a controller, a microcontroller, a microprocessor, other electronic units designed to perform the functions described herein, or a combination thereof.

When the embodiments are implemented in software, firmware, middleware or microcode, program code or code segments, they can be stored in a machine-readable medium, such as a storage component. A code segment may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or programming statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted using any suitable means including memory sharing, message passing, token passing, network transmission, etc.

For a software implementation, the techniques described herein may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The software codes may be stored in memory units and executed by processors. The memory unit may be implemented within the processor or external to the processor, in which case it can be communicatively coupled to the processor via various means as is known in the art.

Referring to fig. 14, illustrated is a system 1400 that effectuates utilizing QoS information in wireless communications. For example, system 1400 may reside at least partially within a mobile device. It is to be appreciated that system 1400 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g., firmware). System 1400 includes a logical grouping 1402 of electrical components that can act in conjunction. For instance, logical grouping 1402 can include an electrical component for establishing a traffic plane function with a network 1404. Further, logical grouping 1402 can include an electrical component for performing quality of service configuration with a network through use of a traffic plane function 1406.

Logical grouping 1402 can also include: means for maintaining quality of service information prior to initiating the communication link, wherein the maintained quality of service information is configured; an electronic component for synchronizing at least one policy between a network entity and a network using an update process, wherein configuring a traffic plane function can be accomplished by using a subscription policy, a policy update, and a latest binding; and/or an electronic component for providing a network with a permanent identification of a network entity; these components may be integrated as part of the electrical component 1404 for identifying a transmission of a control protocol data unit and/or the electrical component 1406 for incrementing a counter by a direct correlation of the identified transmission of the control protocol data unit, as a separate entity, and/or the like. Additionally, system 1400 can include a memory 1408 that retains instructions for executing functions associated with electrical components 1404 and 1406. While electrical components 1404 and 1406 are shown as being external to memory 1408, it is to be understood that one or more of electrical components 1404 and 1406 can exist within memory 1408.

Referring to fig. 15, illustrated is a system 1500 that effectuates utilizing QoS information in wireless communications. For example, system 1500 can reside at least partially within a mobile device. It is to be appreciated that system 1500 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (e.g., firmware). System 1500 includes a logical grouping 1502 of electrical components that can act in conjunction. For instance, logical grouping 1502 can include an electrical component for establishing traffic plane functionality directly with a network entity 1504. Moreover, logical grouping 1502 can include an electrical component for performing quality of service configuration with a network entity through use of a traffic plane function 1506.

Logical grouping 1502 may also include: an electronic component for collecting quality of service information from an access gateway, wherein the access gateway can obtain the quality of service information from a policy change rule function; means for saving quality of service information prior to initiating the communication link, wherein the saved quality of service information can be configured; an electronic component for maintaining a quality of service information fragment, a portion of which is typically used by a network entity; and/or an electrical component for synchronizing at least one policy between the network entity and the network using an update procedure; these components may be integrated as part of the electronic component 1504 for authenticating the control protocol data unit and/or the electronic component 1506 for generating a notification for a module sending the control protocol data unit to reset the counter upon successful authentication of the control protocol data unit, as a separate entity, and/or the like. While electronic components 1504 and 1506 are shown as being external to memory 1508, it is to be understood that electronic components 1504 and 1506 can exist within memory 1510.

Further, other relevant QoS characteristics may be implemented in accordance with aspects disclosed herein. It should be appreciated that the following is for illustrative purposes and is not intended to limit the scope in any way. The system may allow QoS differential IP services (e.g., VoIP and other data services) to be defined and specified separately within the bounds of the air interface. The UMB air interface may support multiple IP streams. Each IP flow may be mapped onto a single save marked by a save label (ReservationLabel), which may be mapped to the flow.

The eBS can communicate data with the access gateway via the PMIP GRE tunnel. The eBS establishes an AT generic GRE tunnel to transmit data frames between the AT and the AGW. A given packet data session may support one or more IP addresses. The PMIP GRE tunnel may carry multiple IP flows. An IP flow may be a series of packets that share a particular instance of an IETF protocol layer. For example, an RTP stream may include packets of an IP protocol instance, all of which may share the same source and destination IP addresses and UDP port numbers.

A QoS architecture may exist in a CAN system. On the forward link, the AGW may copy the DSCP of the inner IP header to the DSCP of the outer IP header, taking into account the DSCP marking authorization received from the HAAA. Upon receiving the IP flow from the AGW, the eBS may use the packet filter received from the AT to map the forward traffic to the corresponding over-the-air save, with different over-the-air QoS treatment.

For the reverse link, the eBS may mark the DSCP of the inner and outer IP headers based on the QoS over the air interface (e.g., QoS flow profile id (flowprofileid)). When the AT and AGW perform access authentication and authorization with the home AAA server, the home AAA server may return the user QoS if the MS is authenticated.

The profile information arrives at the AGW via the visited AAA server. The user QoS profile includes the following 3GPP2 attributes: maximum granted aggregate bandwidth for best effort traffic, granted flow profile IDS for each direction, maximum priority for each flow, inter-user priority (e.g., best effort, QoS traffic, etc.), mapping between flow profile ID and DSCP, mapping between flow profile ID and management rules (e.g., token bucket parameters), allowed Differentiated Services Code Point (DSCP) marking of forward and reverse links, etc.

Allowed Differentiated Services Code Point (DSCP) marking for MIPv4 reverse tunneling may be used. If the AGW (access gateway, such as access gateway 310 of fig. 3) receives the user QoS profile from the home AAA server, the AGW can provide the allowed Differentiated Services Code Point (DSCP) tagged QoS attributes for MIPv4 reverse tunnel in the received user QoS profile (if available) to the SRNC for QoS request authorization and traffic management purposes, among other things.

The AGW may store allowed Differentiated Services Code Point (DSCP) flag attributes for the forward and reverse links and allowed Differentiated Services Code Point (DSCP) flag attributes for the MIPv4 reverse tunnel for subsequent use. In the case of multiple NAIs per AT (e.g., access terminal), the AGW may receive a user QoS profile for each NAI. The AGW can send a corresponding user QoS profile to the SRNC such that the SRNC processes multiple user QoS profiles for each AT.

The AGW can send the local user QoS profile settings to the SRNC as long as the user QoS profile is not included in the AAA message. The QoS profile for each AT may contain the maximum authorized aggregate bandwidth for best effort traffic. If the AGW receives the maximum authorized aggregate bandwidth attribute for best effort traffic from AAA, it can send this attribute to the SRNC through an EAP Access Authentication and Authorization (AAA) procedure. The AN (network, such as network 304 of fig. 3) may use the parameters for admission control and radio resource management. The authorized flow profiles IDS for each direction include a list of authorized flow profiles IDS for ATs in both the forward direction and the reverse direction. Authorized flow list for the AT.

IDS may be different between the forward direction and the reverse direction. The AT requested QoS parameters may contain a set of flow profiles IDS in the forward and reverse directions. If the AGW receives the authorized flow Profile ID attribute from the AAA, it can send this attribute to the SRNC through EAP access authentication and authorization procedures. The AN may enforce the set of authorized profiles by not admitting profile IDs that are not present in the list of authorized flow profile IDs.

The QoS profile for each AT may contain the maximum priority for each flow. If the AGW receives the maximum priority attribute for each flow from AAA, it can send this attribute to the SRNC through an EAP access authentication and authorization procedure. An application in the AT may request flow priority for a particular flow within the QoS scope. The AN may grant about 1 of about 16 possible priority levels, but typically not greater than the authorized maximum priority parameter for each flow in the user's QoS profile. The AN may use the priority value for admission control and resource allocation for the flow. Priority values received from the application that are greater than the maximum priority of authorization for each flow may be reduced to a maximum value. Flows associated with higher priority values may obtain service grants in preference to flows associated with lower priority values. The flows with higher priority values may also be assigned a priority for resource allocation.

The QoS profile for each AT may contain an inter-user priority value. If the AGW receives the inter-user priority value from the AAA, it can send the inter-user priority value to the SRNC through EAP access authentication and authorization procedure. The AN may use the inter-user priority value for scheduling packets on the best network. By assigning the same parameter value to all users, the operator may choose not to use this capability.

The QoS profile of each AT may contain a mapping between the flow profile ID and the DSCP. If the AGW receives the mapping attribute between the flow profile ID and the DSCP from the AAA, it can send the attribute to the SRNC through the EAP access authentication and authorization procedure. The AN may use this attribute for marking reverse link packets based on the granted flow profile ID.

The QoS profile for each AT may contain a mapping between the flow profile ID and the management rules. If the AGW receives the mapping attribute between the flow profile ID and the management rules from the AAA, it can send this attribute to the SRNC through an EAP access authentication and authorization procedure. The AN uses this attribute for managing forward packets based on the admitted flow profile ID. The management rules include token bucket parameters such as peak rate, bucket size, token rate, maximum delay, etc.

The QoS profile for each AT may contain allowed DSCP marking on the forward and reverse links. If the AGW receives the allowed DSCP marking attribute on the reverse link from the AAA, it can send this attribute to the SRNC through the EAP access authentication and authorization procedure. According to the differentiated services standard, the AT may mark the packet (e.g., in the reverse direction). However, the AN can annotate the differentiated services marking that the AT applies to the packet based on the granted QoS, the mapping between the flow profile ID and the DSCP, the allowed DSCP marking on the reverse link and its local policy. The AGW may define the differentiated services marking on the forward link based on DSCP markings allowed on the forward link or based on its local policy.

According to one embodiment, there may be a code point definition where the lower approximately three bits (e.g., 3, 4, and 5) of the code point definition are all zeros. Thus, there may be about eight categories. The default forwarding (commonly referred to as best effort) is a class selector with a class equal to zero. A deterministic forwarding (AF) class and an Expedited Forwarding (EF) class may be used. An attribute may contain three bits: the "A", "E", and "0" bits. When the "a" bit is set, the packet can be marked with an arbitrary AF category. When the "E" bit is set, the packet may be marked with the EF classification. When the "0" bit is set, the packet may be marked with an empirical/local usage classification. The maximum category field may specify the maximum category for which the user or AGW may label the packet.

The QoS profile of each AT may contain allowed DSCP marking for MIPv4 reverse tunneling. If the AGW receives the label, the AGW may store the label and use the label if MIPv4 reverse tunneling is enabled. Differentiated Services Code Points (DSCP) supported in this document may be based on the following RFCs:

the attributes contain the aforementioned approximately 3 bits, "A", "E", and "0". When the "a" bit is set, the packet can be marked with an arbitrary AF category. When the "E" bit is set, the packet may be marked with the EF classification. When the "0" bit is set, the packet may be marked with an empirical/local usage classification. The maximum class field may specify the maximum class for which the AGW may label packets on the FA-HA reverse tunnel. For example, if the largest category is set to selector category 3, all selector categories of selection category 3 are allowed to be reached and included. If the maximum category is set to AF 12. AF 12 and AF 13 flags are allowed. When all three bits are cleared, and when the maximum class is set to 0, the AGW may send MIPv4 reverse tunnel packets marked as best effort. If the home AAA server wants to update the user QoS profile of an authenticated AT (NAI), it can send the user QoS profile information to the AGW via the visited AAA server. The AGW may send the maximum granted aggregate bandwidth for best effort traffic, granted flow profile IDS for each direction, maximum priority for each flow, inter-user priority, mapping between flow profile ID and DSCP, mapping between flow profile ID and management rules, allowed Differentiated Services Code Point (DSCP) marking attributes for forward link and reverse link to the DAP if they are received by the AGW. The AGW may also overwrite the stored allowed Differentiated Services Code Point (DSCP) marking attributes for the forward link and reverse link with the newly received attributes. If the AGW receives an allowed Differentiated Services Code Point (DSCP) flag attribute for the MIPv4 reverse tunnel, it may override the stored allowed Differentiated Services Code Point (DSCP) flag attribute for the MIPv4 reverse tunnel with the newly received attribute. The QoS difference over the backhaul between AN and AGW is based on the IETF DS architecture.

On the forward link, when the AGW receives a packet from the internet, the AGW may copy the DSCP of the inner IP header to the DSCP of the outer IP header, taking into account the allowed DSCP marking parameters and local policy of the forward link received from the HAAA. On the reverse link, when the AGW receives packets from the eBS, the AGW may match the source address of these packets with the source address associated with the authenticated NAI. The AGW may annotate the packet based on the allowed DSCP marking parameters and local policy of the reverse link.

For the forward link, when receiving an IP flow from the AGW, the eBS uses the packet filter received from the AT to map the forward traffic to a corresponding over-the-air hold with different over-the-air QoS treatment. For the reverse link, when an IP flow is received from the AT, the eBS marks the DSCP of the inner and outer IP headers based on the granted QoS over the air interface (e.g., QoS flow profile ID), the QoS profile (mapping attributes between flow profile ID and DSCP and allowed DSCP marking parameters on the reverse link) if the QoS profile is received from the AGW.

If MIPv4 reverse tunneling is enabled, the AGW may copy (e.g., re-label) the DSCP of the inner IP header to the DSCP of the outer IP header for MIP reverse tunneling traffic based on the allowed DSCP label attributes for MIPv4 reverse tunneling received from the home RADIUS server or based on its local policy.

For MIPv4FA mode forward traffic to the AT, the HA may set the differentiated services field of the HA-FA tunnel to the differentiated services class of each received packet bound to the AT based on local policy. For MIPv6 forward traffic to the AT, the HA may set the differential services field of the HA-AT tunnel to the differential service class of each received packet bound to the AT based on local policy.

In addition, there may be other parameters: 1 GRE key per AT for AT-initiated QoS (e.g., AT establishes TFT with AN and performs QoS configuration with AN for AN-initiated QoS; AGW receives QoS information from PCRF and sends it to AN; AN can establish TFT with AT and perform QoS configuration with AT; AN authorizes QoS establishment based on QoS subscription profile received via access authentication and QoS session policy, if any, received from AGW).

The AGW may communicate the QoS session policy and charging rules received from Ty to the AN via the Ty' interface: flow identifiers (e.g., 5-tuple, source/destination IP address/port, protocol, etc.). This may be used for charging and QoS, authorized QoS based on service QCI, GBR, MBR, etc., charging models, offline and online charging based on traffic, duration, etc., gating, etc. The AN may perform packet filtering for OTA QoS processing and the AN may report accounting records to the AGW.

For OTA links, QoS may be implemented by different RLPs having different QoS. For the reverse link, the eBS may flag both established DSCPs. For downlink traffic, the OTA-based eBS inner and outer IP headers perform QoS (e.g., profile ID) for OTA QoS grants, packet filtering of DSCP, and processing based on TFT-received profile ID mapping and allowed DSCP from AGW or AT. The BS may also make a flag, etc.

DSCP of inner and outer IP of the forward link, the AGW may copy the DSCP of the inner header to the DSCP (e.g., profile ID) of the outer IP header based on the TFT and OTA QoS IP header, taking into account DSCP marking authorization.

The QoS user profile (and static policy) can be sent from the HAAA to the SRNC via successful authentication: maximum granted aggregate bandwidth for best effort traffic, granted flow profile IDS for each direction, maximum priority for each flow, allowed differentiated services tag, inter-user priority.

What has been described above includes examples of one or more embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the aforementioned embodiments, but one of ordinary skill in the art may recognize that many further combinations and permutations of various embodiments are possible. Furthermore, the described embodiments are intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term "includes" is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term "comprising" as "comprising" is interpreted when employed as a transitional word in a claim.

Claims (67)

1. A method for initiating quality of service from a network entity, comprising:

establishing a service plane function with a network;

performing quality of service configuration with the network by using the traffic plane function.

2. The method of claim 1, further comprising: quality of service information is saved prior to initiating the communication link, wherein the saved quality of service information is configured.

3. The method of claim 1, further comprising: an update procedure is used to synchronize at least one policy between the network entity and the network.

4. The method of claim 1, configuring the traffic plane function is accomplished by using subscription policies, policy updates, and late bindings.

5. The method of claim 1, further comprising: providing a permanent identification of the network entity to the network.

6. The method of claim 1, further comprising: the quality of service information is maintained based only on partial information of the application.

7. The method of claim 1, further comprising: inter-user priority for quality of service information.

8. The method of claim 1, further comprising: the stored identification space is divided into different spaces to identify network-initiated quality of service or access terminal-initiated quality of service.

9. The method of claim 1, further comprising: multiple IP sessions with different IP addresses are controlled using the same policy session.

10. The method of claim 1, further comprising: the quality of service policy information is encoded or encapsulated within network specific signaling.

11. A wireless communications apparatus, comprising:

the setting-up device establishes the service plane function with the network;

a setter for performing quality of service configuration with the network by using the service plane function.

12. The apparatus of claim 11, further comprising: a recorder that saves quality of service information prior to initiating the communication link, wherein the saved quality of service information is configured.

13. The apparatus of claim 11, further comprising: an equalizer to use an update procedure to synchronize at least one policy between the network entity and the network.

14. The apparatus of claim 11, configuring the traffic plane function is accomplished by using subscription policies, policy updates, and late bindings.

15. The apparatus of claim 11, further comprising: an identifier that provides a permanent identification of the network entity to the network.

16. The apparatus of claim 11, further comprising a token, wherein the token is transmitted to a different network entity for correction of quality of service information.

17. A wireless communications apparatus, comprising:

a module for establishing a service plane function with a network;

means for performing quality of service configuration with the network using the traffic plane function.

18. The apparatus of claim 17, further comprising: means for saving quality of service information prior to initiating the communication link, wherein the saved quality of service information is configured.

19. The apparatus of claim 17, further comprising: means for using an update procedure to synchronize at least one policy between the network entity and the network.

20. The apparatus of claim 17, configuring the traffic plane function is accomplished by using subscription policies, policy updates, and late bindings.

21. The apparatus of claim 17, further comprising: means for providing a permanent identification of the network entity to the network.

22. The apparatus of claim 17, further comprising a token, wherein the token is communicated to a different network entity for correcting QoS information.

23. A machine-readable medium having stored thereon machine-executable instructions for:

establishing a service plane function with a network;

performing quality of service configuration with the network by using the traffic plane function.

24. The machine-readable medium of claim 23, further comprising: instructions for saving quality of service information prior to initiating the communication link, wherein the saved quality of service information is configured.

25. The machine-readable medium of claim 23, further comprising: instructions for using an update procedure to synchronize at least one policy between the network entity and the network.

26. The machine-readable medium of claim 23, configuring the traffic plane function is accomplished by using subscription policies, policy updates, and late bindings.

27. The machine-readable medium of claim 23, further comprising: instructions for providing a permanent identification of the network entity to the network.

28. An apparatus in a wireless communication system, comprising:

a processor to:

establishing a service plane function with a network;

performing quality of service configuration with the network by using the traffic plane function.

29. The method of claim 28, further comprising: the processor is configured to store quality of service information prior to initiating the communication link, wherein the stored quality of service information is configured.

30. The method of claim 28, further comprising: the processor is configured to use an update procedure to synchronize at least one policy between the network entity and the network.

31. The method of claim 28, configuring the traffic plane function is accomplished by using subscription policies, policy updates, and late bindings.

32. The method of claim 28, further comprising: the processor is configured to provide a permanent identification of the network entity to the network.

33. A method for initiating quality of service from a network, comprising:

directly establishing a service plane function with a network entity;

performing quality of service configuration with the network entity by using the traffic plane function.

34. The method of claim 33, further comprising: quality of service information is collected from the access gateway.

35. The method of claim 34, the access gateway obtains the quality of service information from a policy change rule function.

36. The method of claim 33, further comprising: quality of service information is saved prior to initiating the communication link, wherein the saved quality of service information is configured.

37. The method of claim 33, further comprising: and saving the service quality information fragment.

38. The method of claim 37, the network entity uses a portion of the quality of service information fragment.

39. The method of claim 33, further comprising: an update procedure is used to synchronize at least one policy between the network entity and the network.

40. A wireless communications apparatus, comprising:

the constructor directly establishes a service plane function with a network entity;

a manager to perform quality of service configuration with the network entity by using the service plane function.

41. The apparatus of claim 40, further comprising: a collector that collects quality of service information from the access gateways.

42. The apparatus of claim 41, the access gateway obtains the quality of service information from a policy change rule function.

43. The apparatus of claim 40, further comprising: a container that stores quality of service information prior to initiating the communication link, wherein the stored quality of service information is configured.

44. The apparatus of claim 40, further comprising: and the saver is used for saving the service quality information fragment.

45. The apparatus of claim 44, the network entity uses a portion of the quality of service information fragment.

46. The apparatus of claim 40, further comprising: an advancer that employs an update procedure to synchronize at least one policy between the network entity and the network.

47. A wireless communications apparatus, comprising:

a module for establishing service plane functions directly with a network entity;

means for performing quality of service configuration with the network entity using the traffic plane function.

48. The apparatus of claim 47, further comprising: means for collecting quality of service information from an access gateway.

49. The apparatus of claim 48, the access gateway obtains the quality of service information from a policy change rule function.

50. The apparatus of claim 47, further comprising: means for saving quality of service information prior to initiating the communication link, wherein the saved quality of service information is configured.

51. The apparatus of claim 47, further comprising: means for storing the quality of service information fragment.

52. The apparatus of claim 51, the network entity uses a portion of the quality of service information fragment.

53. The apparatus of claim 47, further comprising: means for using an update procedure to synchronize at least one policy between the network entity and the network.

54. A machine-readable medium having stored thereon machine-executable instructions for:

directly establishing a service plane function with a network entity;

performing quality of service configuration with the network entity by using the traffic plane function.

55. The machine-readable medium of claim 54, further comprising: instructions for collecting quality of service information from an access gateway.

56. The machine-readable medium of claim 55, the access gateway obtains the quality of service information from a policy change rule function.

57. The machine-readable medium of claim 54, further comprising: instructions for saving quality of service information prior to initiating the communication link, wherein the saved quality of service information is configured.

58. The machine-readable medium of claim 54, further comprising: instructions for maintaining the quality of service information fragment.

59. The machine-readable medium of claim 58, the network entity uses a portion of the quality of service information fragment.

60. The machine-readable medium of claim 54, further comprising: instructions for using an update procedure to synchronize at least one policy between the network entity and the network.

61. An apparatus in a wireless communication system, comprising:

a processor to:

directly establishing a service plane function with a network entity;

performing quality of service configuration with the network entity by using the traffic plane function.

62. The method of claim 61, further comprising: the processor is configured to collect quality of service information from an access gateway.

63. The method of claim 62, the access gateway obtains the quality of service information from a policy change rule function.

64. The method of claim 61, further comprising: the processor is configured to store quality of service information prior to initiating the communication link, wherein the stored quality of service information is configured.

65. The method of claim 61, further comprising: the processor is configured to store the qos information fragment.

66. The method of claim 65, the network entity uses a portion of the quality of service information fragment.

67. The method of claim 61, further comprising: the processor is configured to use an update procedure to synchronize at least one policy between the network entity and the network.