KR20120058427A - Method and apparatus for configuring subscriber quality of service profiles - Google Patents

Abstract

PURPOSE: A subscriber QoS(Quality of Service) profile configuration method and apparatus thereof are provided to explain signals exchanged between servers by improving the performance of a wireless network apparatus like 3GPP2 HSGW and 3GPP2 AAA. CONSTITUTION: A subscriber QoS profile module constitutes a QoS profile(802). The reception module receives the QoS profile request message through a first wireless network(804). A transmission module transmits a QoS profile response message through the first wireless network(806). The reception module receives a list of supported-features AVP(Attribute-Value Pairs). The transmission module includes a complete set of features within the QoS profile response message.

Description

METHOD AND APPARATUS FOR CONFIGURING SUBSCRIBER QUALITY OF SERVICE PROFILES}

This application is filed on Nov. 29, 2010, US Provisional Application No. 61 / 417,867 “Configuring Subscriber QOS Profile in EHPRD System,” US Provisional Application No. 61 / 429,435, filed January 3, 2011 “Configuring Subscriber QOS Profile in EHPRD System- Part 2 ”, US Provisional Application No. 61 / 434,430, filed Jan. 19, 2011“ Configuring Subscriber QOS Profile in EHPRD System-Part 3 ”, US Provisional Application No. 61 / 449,043, filed March 3, 2011“ Configuring Subscriber QOS Profile in EHPRD System-Part 4 ”, filed April 4, 2011, US Provisional Application No. 61 / 471,685, entitled“ Benefit of Priority of Configuring Subscriber QOS Profile in EHPRD System-Part 5 ”.

All of the content of this patent application is incorporated herein.

The present invention relates to wireless communication in a wireless communication system.

In a packet switched network in which data packets are delivered over a link or network of wired or wireless communication, a quality of service (QoS) is implemented to reserve wireless communication resources. QoS is also implemented to control the delivery of data packets to achieve a certain level of performance in delivering data packets. The level of QoS performance is one of: transmission bit rate, transmission delay, packet data jitter, probability of loss of data, bit error rate, etc. It can be measured by the above parameters. Certain data services can be tolerant of delay and packet drop. On the other hand, certain data services, such as voice over IP (VoIP), interactive data services, video and multimedia data services, can be highly sensitive to delay and packet loss. This requires a high level of QoS.

QoS mechanisms may be implemented by controlling and managing packet delivery over a link or network of wired or wireless communication based on packet switching to meet specific QoS requirements. The wireless communication system includes a mobile device, a cell phone, a wireless air card, a mobile station (MS), a user equipment (UE), an access terminal (AT), a subscriber station (SS), and the like. It may include a network of one or more base stations in communication with one or more wireless devices. Each base station may transmit a wireless signal carrying data such as voice data or other data content to the wireless device. A base station may be called an access point (AP) or an access network (AN), or may be part of an access network. In addition, the wireless communication systems can communicate with each other or with a wired communication system via one or more core networks. The wireless device may use one or more other wireless technologies for communication. Various wireless technologies include code division multiple access (CDMA), high rate packet data (HRPD), global system for mobile communications (GSM) -based technologies, long-term evolution (LTE), orthogonal frequency-division multiplexing (CDMA2000 1x) ) And worldwide interoperability for microwave access (WiMAX). In certain cases, a wireless communication system may include a plurality of networks using different wireless technologies.

There is a need for a technique for QoS configuration.

This disclosure describes techniques for wireless communication.

In one aspect, a wireless communication apparatus operating in a first wireless communication system that implements a first wireless communications protocol is described. The wireless communication device includes a subscriber QoS profile module constituting a quality of service (QoS) profile, a receiving module for receiving a QoS profile request message on the first wireless network, and on the first wireless network. And a transmission module for transmitting the QoS profile response message.

In another aspect, a method of wireless communication is described. The method of wireless communication includes configuring a QoS profile, receiving a QoS profile request message on the first wireless network, and sending a QoS profile response message on the first wireless network.

In another aspect, a computer program product having stored thereon code for configuring a QoS profile, receiving a QoS profile request message on the first wireless network, and sending a QoS profile response message on the first wireless network. ) Is explained.

In another aspect, a computer program product is described that stores apparatus, methods, and instructions for configuring a subscriber quality of service (QoS) profile in a wireless network. The method includes sending a QoS profile request command, receiving a QoS profile response message including a result code, and performing a QoS profile configuration action in response to the result code.

In another aspect, a third generation partnership project 2 (3GPP2) authentication, authorization and accounting (AAA) proxy / server provides data of 3GPP2 subscriber QoS profiles and provides After successful authentication, provide an evolved high rate packet data (eHRPD) serving gateway (HSGW) operable to request information about the subscriber QoS profile of the subscribed user from the 3GPP2 AAA proxy / server, and the requested subscriber QoS profile A computer program product storing apparatus, method and instructions for providing the 3GPP2 AAA proxy / server operative to send information about the HSGW are described.

Details of one or more implementations are set forth in the accompanying drawings, the drawings, and the description below. Other features may be apparent from the description, drawings, and claims.

Various techniques may be provided by the present invention to provide subscriber QoS profiles of a system operating within two different wireless communication networks implementing two different wireless communication protocols.

In addition, the signals exchanged between the 3GPP2 HSGW and the 3GPP2 proxy server to enable subscriber QoS profile queries and responses can be described by the present invention.

In addition, various improvements for wireless network devices, such as 3GPP2 HSGW, 3GPP2 AAA Proxy Server, and 3GPP AAA Proxy Server, may be described in order to enable the present invention to provide subscriber QoS profile information between the 3GPP system and the 3GPP2 system. have.

1 illustrates an example of a wireless communication system.
2 shows an example of a radio station structure.
3 is a block diagram illustrating a non-roaming interworking structure.
4 is a block diagram illustrating a roaming interworking structure.
5 is a block diagram illustrating yet another roaming interworking structure.
6 is a signal exchange diagram illustrating an example of messages exchanged for subscriber QoS profile retrieval during authentication.
7 is a signal exchange diagram illustrating an example of messages exchanged for subscriber QoS profile retrieval during handoff.
8 is a flowchart illustrating a process of wireless communication.
9 is a block diagram illustrating a portion of a wireless communication device.
10 is a flowchart illustrating a process of wireless communication.
11 is a block diagram illustrating a portion of a wireless communication device.
12 is a flowchart illustrating a process of wireless communication.
13 is a block diagram illustrating a portion of a wireless communication device.
14 is a flowchart illustrating a process of wireless communication.
15 is a block diagram illustrating a portion of a wireless communication device.
Like reference symbols in the various drawings indicate like elements.

In the following description, a technique is provided for wireless communication in which a subscriber Quality of Service (QoS) profile is shared between two different cellular communication networks. In one aspect, a server in a first wireless communication system is configured to provide a subscriber QoS profile obtained during user authentication in a second wireless communication system. In addition, as discussed further below, the described techniques may be used to support various wireless communications networks, such as gateway servers, authentication, authorization, and accounting servers (AAA servers). It may be useful in improving the operation of communication devices and servers. Such useful and other useful aspects of the described technology are further described below.

1 illustrates an example of a wireless communication system. The wireless communication system can include one or more base stations (BSs) 105a, 105b, one or more wireless devices 110, and an access network 125. Base station 105 may provide wireless service to wireless devices 110 in one or more wireless sectors. Base stations 105a and 105b include directional antennas to generate two or more directional beams that provide wireless coverage to different sectors.

The access network 125 may communicate with one or more base stations 105a, 105b. The access network 125 may include one or more base stations 105a, 105b. The access network 125 communicates with a core network (not shown in FIG. 1) that provides connectivity with other wireless and wired communication systems. The core network may include one or more service subscription databases that store information related to subscribed wireless devices 110. The first base station 105 may provide a wireless service based on the first radio access technology, and the second base station 105 may provide a wireless service based on the second radio access technology. . The base station 105 may be co-located or separately installed in the ground according to a deployment scenario. The access network 125 may support a plurality of different radio access technologies.

Various examples of a wireless communication system and an access network that can implement the technology and system of the present invention include code division multiple access (CDMA), high rate packet data (HRPD), and evolved HRPD (eHRPD) such as CDMA2000 1x based on a wireless communication system. , Universal mobile telecommunications system (UMTS), universal terrestrial radio access network (UTRAN), evolved UTRAN (E-UTRAN), long-term evolution (LTE) and worldwide interoperability for microwave access (WiMAX). The wireless communication system may include a plurality of networks using different wireless technologies. Dual-mode or multi-mlode wireless devices include two or more wireless technologies that can be used to connect to different wireless networks. The wireless device may support simultaneous voice-data operation (SV-DO).

2 is a block diagram illustrating a portion of a radio station 205. A radio station 205, such as a base station or wireless device, may include processor electronics 210, such as a microprocessor, that implements one or more of the radio technologies proposed herein. The radio station 205 may include transceiver electronics 215 for transmitting and / or receiving wireless signals over one or more communication interfaces, such as the antenna 220. The radio station 205 may include other communication interfaces for transmitting and receiving data. The radio station 205 may include one or more memories configured to store information such as data and / or instructions. The processor electronics 210 may include at least one portion of the transceiver electronics 215.

3 shows an example of an interworking structure between a 3GPP evolved universal terrestrial radio access network (E-UTRAN) and a 3GPP2 evolved high rate packet data (eHRPD) network. E-UTRAN is known as LTE. The structure of FIG. 3 supports interworking interfaces defined in TS 23.402 3GPP: TS 23.402: Architecture Enhancements for non-3GPP Accesses including the interfaces of S101 and S103. S101 is a signaling interface between an EPC mobility management entity (MME) and an eHRPD access network (eAN / ePCF) (3GPP: TS 29.276: Optimized Handover Procedures and Protocols Between E-UTRAN Access and cdma2000 HRPD Access-Stage 3) . eAN / ePCF functionality is defined in A.S0022-0 (3GPP2: A.S0022-0: E-UTRAN-HRPD Connectivity and Interworking: Access Network Aspects (E-UTRAN-HRPD IOS),). S103 is a bearer interface between an evolved packet core (EPC) serving gateway (S-GW) and an evolved high rate packet data (eHRPD) serving gateway (HSGW) (see 3GPP TS 29.276). The eHRPD network provides an IP environment that supports attachment to a plurality of packet data networks (PDNs). In addition, the eHRPD network supports the assignment of IPv4 addresses or IPv6 addresses or addresses of both IPv4 and IPv6 for each PDN through the 3GPP evolved packet core (EPC). The eHRPD terminal 110 uses network-based mobility and relies on the use of proxy mobile IPv6 (PMIPv6) in the network for mobility management. The HSGW is a trusted non 3GPP access network that is an HRPD serving gateway that connects an eHRPD access network to an evolved packet core (EPC). The terminal 1100 is in communication with the eNodeB 302 over a wireless protocol such as the LTE wireless protocol.

4 illustrates an interworking roaming structure of E-UTRAN to eHRPD for home-routed traffic. At this time, the anchor point (P-GW) 710 is located in the home network. The wireless network 400 also includes a home public land mobile network (HPLMN) 424 and a vista PLMN (VPLMN). In addition, FIG. 4 illustrates terminals 110 in mobile communication with the corresponding eNodeB 302 and the HRPD base station (BTS), and the E-UTRAN / EPC 420 and the eHRPD 422.

5 shows an interworking roaming structure of E-UTRAN to eHRPD for local breakout traffic. At this time, the anchor point (P-GW) 710 is located in the visited network. The wireless communications network 500 also includes an HPLMN 524 and a VPLMN 526. In addition, FIG. 5 shows an E-UTRAN / EPC 520 and an eHRPD 522 together with various devices for network interworking.

As shown in each of the wireless networks 300, 400, and 500 of FIGS. 3 to 5, the following reference points may be defined for interworking of the E-UTRAN and the eHRPD.

H1 / H2 reference point: The H1 reference point may carry signaling information between an S-HSGW (source HSGW) and a T-HGSW (target HSGW) for handoff between optimized HGSWs.

The H2 reference point may carry uplink and downlink user traffic from the S-HSGW to the T-HGSW for optimized inter-GSG handoff.

Gxa reference point: The Gxa reference point may connect the PCRF (policy and charging rules function 712) in the 3GPP EPC and the BBERF of the HSGW in the 3GPP2 eHRPD access network. Detailed requirements and operation of this interface are defined in the 3GPP TS 23.203, TS 29.212 and TS 29.213 documents.

Pi ^* Reference Point: The protocol used on Pi ^* reference point can connect the HSGW with a 3GPP2 AAA proxy. The protocol used on the Pi * reference point may be similar to the protocol used on the STa reference point with the further enhancement described herein.

S101 reference point: The S101 reference point may connect the MME 304 in the 3GPP EPS and the eAN / ePCF 306 in the 3GPP2 eHRPD access network according to 3GPP2 A.S0022-0. The S101 reference point may provide tunneling of data and signaling between the terminal 110 and the destination access network through the source / serving access network. Detailed operation of this interface is defined in the 3GPP TS 23.402 and TS 29.276 documents.

S103 reference point: The S103 reference point may connect an H-SGW in a 3GPP eHRPD network with a serving gateway 308 in the 3GPP EPC. The S103 reference point forwards downlink data between the S-GW 308 and the HSGW to minimize packet loss when moving from the E-UTRAN to the eHRPD. Detailed requirements and operation of this interface are defined in the 3GPP TS 23.402 and TS 29.276 documents.

S2a reference point: The S2a reference point may connect the PDN gateway in the 3GPP EPC and the HSGW in the 3GPP2 eHRPD network. The S2a reference point provides a user plane with associated control and mobility support between the eHRPD connection and the P-GW. Detailed requirements and operation of this interface are defined in the 3GPP TS 23.402 and TS 29.275 documents.

STa reference point: The STa reference point may connect an AAA server / proxy in the 3GPP EPC and an AAA proxy in the 3GPP2 eHRPD network. The STa reference point is used to authenticate and authorize the terminal 110. The STa reference point also carries the PMIPv6 mode associated with the Diameter parameter between the 3GPP AAA Server / Proxy 316 and the 3GPP AAA Proxy 318. Detailed requirements and operation of this interface are defined in the 3GPP TS 23.402 and TS 29.273 documents.

Various entities in FIGS. 3-5 may include the following functionality.

eAN / ePCF 306: The eAn / ePCF is an evolved packet (ePCF) that manages the relay of packets between a logical entity in the RAN (radio access network) used for wireless communication with the terminal 110 and the eAN and the HSGW. control function entity).

evolved HRPD (eHRPD) 312: The eHRPD network supports attachment to an evolved packet core (EPC) of 3GPP. The eHRPD network optionally supports smooth handoff between the E-UTRAN and evolved HRPD of single-radio terminals.

Evolved packet core (EPC): The structure of an EPC is defined in the 3GPP TS 23.401 and TS 23.402 documents.

Evolved packet system (EPS): EPS is defined in 3GPP TS 23.003, TS 23.401 and TS 23.402 documents. EPS consists of EPC and E-UTRAN.

HSGW 310: HSGW is a HRPD serving gateway that connects an eHRPD access network to an evolved packet core (EPC) as a trusted non-3GPP access network. The HSGW provides a PMIPv6 mobile access gateway (MAG) function to support layer 3 mobility with the P-GW (LMA).

Mobility between HSGWs due to context transfer: Mobility between HSGWs due to context transfer uses the H1 interface for the source HSGW to transmit the context for the terminal 110 and the H2 interface for data packet forwarding. Occurs when sending to the destination HSGW.

Mobility between HSGWs without context transfer: Mobility between HSGWs without context transfer occurs when there is no H1 / H2 connection between the source HSGW and the destination HSGW, or for some reason the signaling exchange by context transfer fails.

Legacy AT: Legacy AT is defined as an AT conforming to the 3GPP2 X.S0011 document. Legacy ATs may not properly communicate with the HSGW as defined in the 3GPP2 X.S0011 document. The use of “AT” in the 3GPP2 X.S0011 document implies a legacy AT function or terminal 110 function as a legacy AT.

Legacy PDSN: A legacy PDSN is defined as a PDSN that conforms to the 3GPP2 X.S0011 document. Use of “PDSN” implies legacy PDSN.

In the high rate packet data (HRPD) system defined by 3GPP2, the subscriber QoS profile is returned to the PDSN during the authentication procedure when the terminal 110 connects to the network. The PDSN uses some of the attributes from the subscriber QoS profile for authorization of the A10 connection. The PDSN also provides some of the QoS attributes to the RAN where possible for QoS request authorization and traffic monitoring purposes.

The subscriber QoS profile is defined in the 3GPP2 X.S0011 (cdma2000 Wireless IP Network Standard) document. The subscriber QoS profile used in the HRPD system may have the following attributes.

(A) The Maximum Authorized Aggregate Bandwidth for Best-Effort Traffic

(B) The Authorized Flow Profile IDs for each direction

(C) The Maximum per Flow Priority

(D) The Allowed Differentiated Services Markings

(E) The Service Option Profile

(F) The Inter-User Priority for best effort traffic

Within the eHRPD system specified in the 3GPP2 X.S0057-0 (E-UTRAN-eHRPD Connectivity and Interworking: Core Network Aspects) document, a policy and charging control (PCC) framework is applied to QoS control. The PCRF 712 provides a QoS policy to the HSGW through the Gxa interface. The X.S0057-0 document describes only the <QCI, MBR, GBR> parameters that can be mapped to Flow Profile IDs in the HSGW. In addition, the remaining QoS attributes defined in the subscriber QoS profile in the 3GPP2 X.S0011 document are also useful for QoS grant, but it is not clear how to derive these QoS attributes in the implementation of the X.S0057-0 document. For example, in the X.S0011 document, 'The Inter-User Priority for best effort traffic' is used to distinguish the priority of optimal efficiency traffic used by different users. It is applied by an operator. Similarly, other parameters specified in the X.S0011 document may be useful, but a framework for the implementation of those parameters in the X.S0057-0 document is not yet available.

In addition, the implementation of the PCC is optional in the X.S0057-0 document, and the PCC may not be deployed at initial deployment of the eHRPD system. For example, operators can upgrade their HRPD network to an eHRPD network without a PCC as it evolves into the first phase network. Therefore, it is not clear how the HSGW and the eAN will obtain a QoS profile to perform admission control.

Thus, to ensure that the HSGW and eAN can perform QoS functions without PCC, it may be desirable for subscriber QoS profile parameters defined in the 3GPP2 X.S0011 document to be available in the eHRPD system as well. If there is no PCC, when the terminal 110 is authenticated and the HSGW forwards some of the QoS parameters from the subscriber QoS profile to the eAN via an A11 signaling message, the HSGW may operate to obtain the subscriber QoS profile.

In general, the HSGW may obtain a subscriber QoS profile in other ways. As an example, the 3GPP subscriber QoS profile is configured in the 3GPP AAA / HSS (home subscriber server) 320. The subscriber QoS profile configured as above is forwarded to the HSGW 310 by 3GPP AAA on the STa interface and the Pi ^* interface when the terminal 110 is authenticated. The subscriber QoS profile may be stored in 3GPP AAA or HSS 320 in 3GPP format or 3GPP2 format. If the subscriber QoS profile is stored in 3GPP format, QoS mapping to 3GPP2 may be performed at the 3GPP2 AAA proxy server or HSGW. The STa and Pi ^* interfaces may be enhanced to support transmission of subscriber QoS profiles from 3GPP AAA to HGSW 310. Improvements in these 3GPP documents entail non-3GPP access specific details.

As another example, the 3GPP2 subscriber QoS profile is configured at the 3GPP2 AAA proxy / server. During a successful authentication or authentication process for a user, the HSGW 310 requests a subscriber QoS profile from the 3GPP2 AAA proxy / server. The Pi ^* reference point is then enhanced to support subscriber QoS profile parameters, which is limited to the 3GPP2 domain.

An example of implementing the 3GPP2 subscriber QoS profile in detail within a 3GPP2 AAA proxy / server that provides the 3GPP2 subscriber QoS profile to the HSGW 310 in response to a request from the HSGW 310 is as follows.

Pi ^* Reference point supports STa Diameter Application as specified in 3GPP TS 29.273. Also, optionally, the Pi * reference point may support Pi ^* 3GPP2 Diameter Application as specified herein. Both HSGW 310 and 3GPP2 AAA proxy servers are required to support the STa Diameter Application, thus advertizing support for the Sta Diameter Application during the Diameter Capability Exchange process.

When the STa Diameter Application is used, the 3GPP2 AAA proxy server may proxy messages between the GSGW 310 and the 3GPP AAA server.

HSGW 310 or 3GPP2 AAA proxy server that supports 'subscriber QoS profile configuration' may advertise support for Pi * 3GPP2 Diameter Application, for example, during the Diameter Capability Exchange process.

Peers are Pi ^* 3GPP2 of 'Diameter APPL-ID' as Vendor-ID attribute is set to SMI Network management Private Enterprise Codes assigned to 3GPP2 (5535) and Auth-Application-ID is assigned by IANA. Include Vendor-Specific-Application-ID VSA in Diameter Capability Exchange Request set to Diameter Application ID.

As described herein, Pi ^* 3GPP2 Diameter Application may be used when both the 3GPP2 AAA Proxy Server and the HSGW 310 support it.

Pi ^* 3GPP2 Diameter Application is defined as peer entities between HSGW 310 and 3GPP2 AAA Proxy Server. The operator may choose to extend the Pi ^* 3GPP2 Diameter Application between the HSGW 310 and the 3GPP2 AAA server in the home domain. In the latter case, the 3GPP2 AAA proxy server may act as a proxy agent as specified in RFC3588. For example, Pi ^* 3GPp2 Diameter Application specifies the following command to support the characteristics of subscriber QoS profile configuration.

Query profile request (QPR) QPR CMDCODE Query profile answer (QPA) QPR CMDCODE

A query profile request / answer (QPR / QPA) includes a command pair and may be implemented as a set of 'features'. Each feature may be specified by use of a Supported-Feature AVP. Supported-specific settings of the Feature-List-ID and the Feature List sub AVP pair in the AVP are used to indicate the support of a specific feature. Each bit in the feature list sub AVP is independent of the other bits. QPR / QPA command pairs are specified within the ANBF format. For example, 3GPP2 subscriber QoS profile configuration (SubQoSConfig) may be specified for Pi ^* 3GPP2 Diameter Application.

For example, the subscriber QoS profile configuration process uses the support characteristic AVP as follows.

Supported characteristics of the 'M' bit AVP is set in the 'Request' command.

The vendor ID sub AVP is set to 3GPP2 SMI Network Management Private Enterprise Code assigned to 3GPP2 5535.

-The property list ID sub AVP is set to '1'.

The feature list sub AVP has a '0' bit with the bit mask set to one.

For example, the following table defines the feature bits used for the support feature AVP within the QPR / QPA command.

Characteristic bits characteristic M / O Explanation 0 SubQoSConfig M Subscriber QoS Profile Configuration Procedure.

This property allows for the construction of a subscriber QoS profile in the eHRPD system. The subscriber QoS profile is obtained from the 3GPP AAA proxy / server in the home area.

This property is applicable for QPR and QPA instruction pairs.

If the HSGW 310 and 3GPP2 AAA proxy / server support Pi ^* 3GPP2 Diameter Application, the HSGW 310 obtains the subscriber QoS profile from the 3GPP2 AAA proxy / server in the home area by sending a query profile request (QPR) command. Initialize it. If the HSGW 310 does not know that the 3GPP2 AAA proxy / server supports the 'SubQoSConfig' feature, the HSGW 310 includes the support feature AVP in the QPR command. The 3GPP2 AAA Proxy / Server responds with a query profile answer (QPA) command that includes a total set of supported features therefrom within the supported features AVP. If the 3GPP2 AAA proxy / server supports the subscriber QoS profile configuration process and has an available subscriber QoS profile, the 3GPP2 AAA proxy / server processes the subscriber QoS profile information in the QPA command in the process of successfully processing QPR. Returns with the SUCCESS result code.
Feature Bits: Number of bits in the Supported Feature AVP, set to "1".
Attribute: A short name used to represent bits and bone attributes.
M / O: Defines whether the implementation of this feature is mandatory (“M”) or optional (“O”).
Description: A description of this property.

A query profile-request (QPR) command indicated by the “R” bit set in the Command-Code field and the Command Flags field set to the QPR CMDCODE is transmitted from the HSGW 310 to the 3GPP AAA Proxy / Server.

<Example of message format>

<Query Profile-Request> :: = <Diameter Header:

QPR CMDCODE, REQ, PXY, Diameter APPL-ID>

<Session-Id>

{Vendor-Specific-Application-Id}

{Auth-Session-State}

{Origin-Host}

{Origin-Realm}

{Destination-Host}

{Destination-Realm}

{User-Name}

* [Supported-Features]

* [AVP]

* [Proxy-Info]

* [Route-Record]

A query profile-answer (QPR) command indicated by a cleared “R” bit in the Command-Code field and the Command Flags field set to the QPR CMDCODE is sent from the 3GPP AAA Proxy / Server to the HSGW 310.

<Message format>

<Query Profile-Answer> :: = <Diameter Header:

QPR CMDCODE, PXY, Diameter APPL-ID>

<Session-Id>

{Vendor-Specific-Application-Id}

[Result-Code]

[Experimental-Result]

{Auth-Session-State}

{Origin-Host}

{Origin-Realm}

{User-Name}

* [Redirect-Host]

* [Supported-Features]

[Allowed-DiffServ-Markings]

[Service-Option-Profile]

[Maximum-Authorized-Aggregate-Bandwidth]

[Authorized-Flow-Profile-IDs-for-the-User]

[Inter-User Priority]

[Max-Per-Flow-Priority]

* [AVP]

* [Failed-AVP]

* [Proxy-Info]

* [Route-Record]

For example, the subscriber QoS profile configuration process may be implemented as follows. The subscriber QoS profile configuration process may be supported when the HSGW 3130 and the 3GPP2 AAA proxy / server support Pi ^* 3GPP2 Diameter Application. The deployment of Pi ^* 3GPP2 Diameter Application is assumed to be consistent throughout the operator network.

The subscriber QoS profile configuration process can be mapped to the command pair QPR / QPA (query profile request / answer0) defined for Pi ^* 3GPP2 Diameter Application. used to query.

<Retrieve subscriber QoS profile information (retrieval)-authenticating>

6 shows a process of recovering subscriber QoS profile information during terminal 110 authentication. The terminal 110 performs authentication with the 3GPP AAA using the EAP-AKA 'through the 3GPP2 AAA proxy and the authenticator of the HSGW 310. For example, after successful authentication, HSGW 310 initiates a subscriber QoS profile low retrieval process with the 3GPP2 AAA proxy / server. As another example, during validation of a subscriber QoS profile information request from the HSGW 310, the 3GPP2 AAA proxy / server returns the subscriber QoS profile information to the HSGW 310 on a Pi ^* reference point if possible.

The user is authenticated with the 3GPP AAA through the EAP-AKA certification process. For example, steps 1 to 23 of section 5.2.5.1 of document X.S0057-A are successfully completed.

HSGW 310 activates the subscriber QoS profile configuration process by sending a query profile request (QPR) command to the 3GPP2 AAA proxy / server. If the HSGW 310 does not know whether the 3GPP2 AAA proxy / server supports the SubQoSConfig process, the property list ID AVP in the supported property AVP is set to '1', and the property bit '0' of the property list AVP is set to '1'. Is set to. HSGW 310 uses this process to retrieve subscriber QoS profile information from the 3GPP2 AAA proxy / server.

If the query profile request (QPR) command is successfully processed, the 3GPP2 AAA proxy / server responds to the HSGW 310 with a query profile answer (QPA) command with a result code success (DIAMETER_SUCCESS) containing the subscriber QoS profile information. . If the Supporting Feature AVP is included in the QPR command, the Supporting Feature AVP may also be included, supporting a complete set of features supported by the 3GPP2 AAA Proxy / Server. The 3GPP2 AAA proxy / server uses an IMSI-based network access identifier (NAI) as a key for subscriber profile information.

When the HSGW 310 receives the subscriber QOS profile information from the 3GPP2 AAA proxy / server, the HSGW 310 forwards the subscriber QoS profile information elements to the eAN / ePCF through an A11-session update process.

<Subscribe subscriber QoS profile information-handoff in eHRPD due to context transfer and HSGW relocation>

Referring to FIG. 7, during handoff in eHRPD due to context transfer and HSGW relocation, the subscriber QoS profile information context is not transferred from the source HSGW (S-HSGW, 706) to the destination HSGW (T-HSGW, 708). The T-HSGW performs subscriber QoS profile information retrieval with the 3GPP2 AAA proxy / server 318 after receiving the H1-Ack message from the S-HSGW 706.

An example of this process assumes that the introduction of subscriber QoS profile configuration properties is consistent throughout the operator network.

It is assumed that the terminal 110 has an active session with the P-GW through the S-eAN / ePCF and the S-HSGW 706. The terminal 110 or the S-eAN 702 determines whether the terminal 110 moves to the T-eAN 704. The eHRPD radio session context is delivered to the T-eAN including the H1 address of the S-HSGW. The T-eAN / ePCF establishes an A10 connection with the selected T-HSGW 708. The T-HSGW 708 performs a handover initiate process with the S-HSGW on the H1 interface. The S-HSGW responds with a handover Ack that includes user session context parameters. Context parameters associated with the subscriber QoS profile are not passed from the S-HSGW 706 to the T-HSGW 708. Steps 0 through 7 in Section 12.1.1 of the 3GPP2 X.S0057-A document and steps 0 through 7 in Section 12.2 of the 3GPP2 X.S0057-A document illustrate this process.

T-HSGW activates the subscriber QoS profile configuration process by sending a query profile request (QPR) command to the 3GPP2 AAA proxy / server. If the HSGW does not know whether the 3GPP2 AAA proxy / server supports the SubQoSConfig procedure, the feature list ID AVP in the supported feature AVP is set to '1' and the feature bit '0' in the feature list AVP is set to '1'. T-HSGW uses this process to retrieve subscriber QoS profile information from the 3GPP2 AAA proxy / server.

If the query profile request (QPR) command is successfully processed, the 3GPP2 AAA Proxy / Server responds to the T-HSGW with a query profile answer (QPA) command with a result code success (DIAMETER_SUCCESS) containing the 3GPP2 subscriber QoS profile information. . If the Supporting Feature AVP is included in the QPR command, the Supporting Feature AVP may also be included in the QPA command while supporting a complete set of features supported by the 3GPP2 AAA Proxy / Server. The 3GPP2 AAA Proxy / Server uses an IMSI-based network access identifier (NAI) as a key for subscriber profile information.

When the T-HSGW receives the subscriber QOS profile information from the 3GPP2 AAA proxy / server, the T-HSGW forwards the subscriber QoS profile information elements to the eAN / ePCF through the A11-session update process.

As an example, the remaining handoff process continues, for example, in Sections 12.1.1 and 12.2 of the 3GPP2 X.S0057-A document.

The subscriber QoS profile configuration process is initiated by the HSGW. The 3GPP2 AAA Proxy / Server responds with subscriber QoS profile information if possible. As specified in the X.S0011 document, the following attributes of the subscriber QoS profile may be sent to the eAN / ePCF.

Maximum Authorized Aggregate Bandwidth for Best-Effort Traffic

Authorized Flow Profile IDs for Each Direction

Maximum per Flow Priority

Service Option Profile

Inter-User Priority for Best Effort Traffic

As an example, handling and usage of subscriber QoS profile attributes in an HSGW is described in Table 7 and may be performed as specified herein. As an example, the HSGW stores subscriber QoS profile attributes.

Table 3 provides an example of the information elements supported for the QPR command.

Information element name Mapping to Diameter AVP Cat. Explanation Subscriber Identification
(IMSI)
User-Name (see IETF RFC 3588) M Includes subscriber IMSI and is formatted by 3GPP TS 23.003 [xx] Section 2.2. Authentication session state Auth-Session-State
(See IETF RFC 3588) M Contains the value of NO_STATE_MAINTAINED. Support characteristics
Supported-Features
(See 3GPP TS 29.229) O Grouped AVPs. Vendor ID AVP is set to set to SMI Network Management Private Enterprise Codes assigned to 3GPP2 5535. The property list ID AVP is set to '1'. The feature list AVP has a set of '0' bits indicating support for 'SubQoSConfig' (subscriber QoS profile configuration).

Table 4 provides an example of the information elements supported for the QPA command.

Information element name Mapping to Diameter AVP Cat. Explanation Result code Result-Code / Experimental-Result
(See RFC3588).
M Contains the results of the operation.

The action code AVP is used to indicate success or error as defined in the Diameter Base Protocol [see RFC3588 [xx]].

Experimental-result AVP is used for Pi ^* 3GPP2 Diameter Application and related subscriber QoS profile Configuration feature errors. This is a grouped AVP and includes the 3GPP2 Vendor ID 5535 of the Vendor ID AVP and the error code of the Experiment Code AVP. Subscriber Identification
(IMSI) User-Name (see RFC 3588) M Includes subscriber IMSI and is formatted according to 3GPP TS 23.003 [xx] Section 2.2. Authentication session state Auth-Session-State
(RFC 3588 Article) M Contains the value of NO_STATE_MAINTAINED. 3GPP2 AAA Server Name Redirect-Host
(See RFC 3588) C When the result code value is set to DIAMETER_REDIRECT_INDICATION, it is transmitted. It includes Diameter identifier of 3GPP2 AAA server currently serving subscriber in home area. It is never included in the QPA command, or it is included multiple times. Support characteristics
Supported-Features
(See 3GPP TS 29.229) C Grouped AVPs. Vendor ID AVP is set to SMI Network Management Private Enterprise Codes assigned to 3GPP2 5535. The property list ID AVP is set to '1'. Feature List AVP has bits set for the complete set of features supported by the 3GPP2 AAA Proxy / Server. Service option profile
(See X.S0011) Service-Option-Profile
O Can be included if the result code is DIAMETER_SUCCESS. AVP grouped, indicating the maximum number of allowed link flows and allowed service options. Maximum permitted aggregate bandwidth for optimally efficient traffic (see X.S0011). Maximum-Authorized-Aggregate-Bandwidth-for-Best-Effort-Traffic
O If the result code is DIAMETER_SUCCESS, it can be included and indicates the maximum bandwidth that can be allocated to the user for optimal efficiency traffic. Permitted flow profile ID for each direction (see X.S0011) Authorized-Flow-Profile-IDs-for-the-User
O Can be included if the result code is DIAMETER_SUCCESS. A grouped AVP, indicating the flow profile ID that the user is allowed to request in the QoS Sub Blob. Priority within the user for optimal efficiency traffic (see X.S0011) Inter-User-Priority
O If the result code is DIAMETER_SUCCESS, it can be included and indicates the priority within the user that can be allocated to the user's packet flow for optimal efficiency traffic. Maximum flow priority (see X.S0011) Max-Per-Flow-Priority-for-the-User
O If the result code is DIAMETER_SUCCESS, it can be included and indicates the maximum priority that can be allocated to the user's packet flow.

For example, if both HSGW and 3GPP2 AAA proxy / server support Pi ^* 3GPP2 Diameter Application and HSGW needs subscriber QoS profile information, HSGW sends a query profile request (QPR) command to the 3GPP2 AAA proxy / server. Initialize the subscriber QoS profile configuration process. If the HSGW does not know whether the 3GPP2 AAA Proxy / Server supports the SubQoSConfig process, the QPR command may specify the support attribute AVP of the 'M' bit set, the attribute list ID sub AVP set to '1', and the subscriber QoS profile configuration process. Feature list sub AVP with a '0' bit set indicating the request. The HSGW uses this process to retrieve subscriber QoS profile information from the 3GPP2 AAA proxy / server.

For example, the subscriber QoS profile configuration process is a stateless process. As an example, the HSGW includes an Auth-Session-State AVP in which a value is set to NO_STATE_MAINTAINED in a query profile request (QPR) command.

Receiving a query profile answer (QPA) command from the 3GPP2 AAA proxy / server, the HSGW can check the result code. If the result code indicates different from success (DIAMETER_SUCCESS), the HSGW performs a corrective action based on the received result code.

Receiving a query profile answer (QPA) command from the 3GPP2 AAA proxy / server, if the result code is success (DIAMETER_SUCCESS), the HSGW can confirm the presence of subscriber QoS parameters listed in Table 5. In addition, the HSGW can process the parameters in each of the procedures described in Table 4.

For example, when a query profile answer (QPA) command receives an Experimental-Result-Code AVP set to DIAMETER_ERROR_FEATURE_UNSPPORTED or a Result Code AVP set to DIAMETER_AVP_UNSPPORTED, the HSGW stops configuring the 3GPP2 subscriber QoS profile.

Receiving a query profile request (QPR) command, the 3GPP2 AAA proxy / server may do any of the following:

For example, if all the features indicated in the support feature AVP are supported, the 3GPP2 AAA proxy / server includes in the QPA command a support feature AVP that identifies the complete set of features that support Pi ^* 3GPP2 Diameter Application.

For example, if not all of the attributes indicated in the Supporting Attributes AVP are supported, then the 3GPP2 AAA Proxy / Server is set to DIAMETER_EORROR_FEATURE_UNSPPORTED and the experiment includes the Supporting Attributes AVP, which identifies a complete set of features that support Pi ^* 3GPP2 Diameter Application. Returns a QPA command with a result code.

For example, if the support characteristic AVP is not supported, the QPA command is returned with the action code AVP set to DIAMETER_AVP_UNSUPPORTED. The QPA command includes a failed AVP that includes the support characteristic AVP as received in the QPR command.

For example, when the 3GPP2 AAA proxy / server includes the support feature AVP in a query profile answer (QPA), the support feature AVP has an 'M' bit that is empty. In the grouped AVPs, the property list ID sub AVP is set to '1'. Feature list sub AVP has a set of bits for a complete set of features supported by the 3GPP2 AAA proxy / server.

For example, if the 3GPP2 AAA Proxy / Server supports the Subscriber QoS Profile Configuration (SubQoSConfig) property,

The 3GPP2 AAA Proxy / Server checks whether the User Name (IMSI) in the User-Name AVP is known. If not known, a result code of DIAMETER_ERROR_USER_UNKNOWN is returned.

As an example, if the user is known but does not have any subscriber QoS profiles configured for it, the 3GPP AAA Proxy / Server responds with an experimental result code of DIAMETER_ERROR_NO_SUBSCRIBER_QoS_PROFILE.

For other errors, a result code of DIAMETER_UNABLE_TO_COMPLY may be returned.

For example, the subscriber QoS profile configuration process is not controlled. As an example, the 3GPP AAA Proxy / Server includes an authentication session state AVP with a value set to NO_STATE_MAINTAINED in a query profile request (QPR) command.

For example, if a 3GPP2 AAA proxy / server successfully processes a received query profile request (QPR) command, the 3GPP2 AAA proxy / server may query a query profile answer that includes subscribed QoS information as listed in Table 4. ) Command with a result code success (DIAMETER_SUCCESS).

The result code AVP value defined in the Diameter Base Protocol RFC 3588 may be applied.

For example, if one of the result codes defined below is included in the response command, it is included in the experiment result AVP in which the vendor ID is set to the 3GPP2 vendor ID 355.

The experiment result code AVP contains a 3GPP2 assigned value indicating the result of request command processing.

DIAMETER_ERROR_FEATURE_UNSUPPORTED (3001): This test result code is sent to the HSGW by the 3GPP2 AAA proxy / server if it does not support all the features indicated in the supported feature AVP.

DIAMETER_ERROR_NO_SUBSCRIBER_QoS_PROFILE (4001): This test result code is sent to the HSGW by the 3GPP AAA Proxy / Server if the user is known but does not have any subscriber QoS profiles configured for it.

Tables 5 and 6 list examples of Diameter AVPs defined for subscriber QoS profile configuration properties in a query profile request (QPR) and query profile answer (QPA) command.

AVP flag rules Attribute name AVP code Value time Opt May Should not Not May Encr. Service-Option-Profile TBD Grouped V M No Max-Authorized-Aggregate-Bandwidth-for-Best-Effort-Traffic TBD Unsigned32 V M No Authorized-Flow-Profile-IDs-for-the-User TBD Grouped V M No Inter-User-Priority TBD Integer32 V M No Max-Per-Flow-Priority-for-the-User TBD Integer32 V M No ProfileID-Forward 35 Integer32 V M No ProfileID-Reverse 36 Integer32 V M No ProfileID-Bi-Directional 37 Integer32 V M No Max-Link-Flows TBD Unsigned32 V M No Service-Option-Number TBD Unsigned32 V M No NOTE: The AVP header, denoted by "M", indicates whether AVP support is required. The AVP header, indicated by "V", indicates whether an optional vendor ID field is present in the AVP header. More details can be found in IETF RFC 3588.

Attribute name Reference Explanation User-Name RFC3588 Contains the identifier of the subscriber. Supported-Features TS 29.229 Contains a list of properties supported by the Origin Host that initiated the command. Feature-List-ID TS 29.229 Contains an identifier for the property list. Feature-List TS 29.229 It contains a bit mask that indicates the supported characteristics of the application.

Service-Option-Profile AVP (AVP code 5535 / TBD) is a group type. The service option profile AVP specifies authorized packet data service options and allowed maximum number of simultaneous link flows.

As an example, the format of the service option profile AVP is as follows.

Service-Option-Profile :: = <AVP Header: TBD 5535>

{Max-Link-Flows}

* [Service Option Number]

* [AVP]

The Max-Authorized_Aggregate-Bandwidth-for-Best-Effort_Traffic AVP (AVP code 5535 / TPD) is of type Unsigned32. This indicates the maximum bandwidth (binary value of the maximum allowed aggregate bandwidth in bits per second) from 1 to 2 ** 32 that can be allocated to the terminal for optimal efficiency traffic.

Authorized-Flow-Profile-IDs-for-the-User AVP (AV code 5555 / TBD) is a grouped AVP. This provides a list of flow profile IDs that the subscriber is allowed to specify or request in QoS_Sub_Blob.

As an example, the format of Authorized-Flow-Profile_IDs AVP is as follows.

Authorized-Flow-Profile-IDs-for-the-User :: = <AVP Header: TBD 5535>

* [ProfileID-Forward]

* [ProfileID-Reverse]

* [ProfileID-Bi-direction]

* [AVP]

Inter-User-Priority AVP is Integer32. This indicates the priority among users assigned to the terminal for optimal efficiency traffic. For example, low order 3 bits indicate inter-user priority used for scheduling packets (X.S0011). Priority 7 is highest and priority 0 is lowest.

000-011: Priority 0 ~ 3 for general subscribers

100-111: priority 4 ~ 7 for reserved class

The Max-Per-Flow-Priority-for-the-User AVP (AVP code 5535 / TBD) is an Integer32. This indicates the maximum priority that can be assigned to the user's packet flow. The low order 4 bits indicate the maximum priority that a user can specify for packet data flow. Priority 15 is highest and priority 0 is lowest.

0000-0111: Priorities 0-7 for general subscribers

1000-1111: priority 8-15 for reserved class

Profile ID-Forward AVP (AVP code 5535/35) is of type Integer32. This is used to indicate the flow profile ID that the user is allowed to request on the forward link. As an example, the flow profile ID is included in the least significant 16 bits. The most significant 16 bits are set to zero.

ProfileID-Reverse AVP (AVP code 5535/36) is of type Integer32. This is used to indicate the flow profile ID that the user is allowed to request on the reverse link. As an example, the flow profile ID is included in the least significant 16 bits. The most significant 16 bits are set to zero.

ProfileID-Bi-Direction AVP is of type Integer32. This is used to indicate the flow profile ID that the user is allowed to request bi-directionally. As an example, the flow profile ID is included in the least significant 16 bits. The most significant 16 bits are set to zero.

Max-Link-Flows AVP is of type Unsigned32. This indicates the maximum number of link flows that the user is allowed to establish.

Service-Option-Number AVP is of type Unsigned32. This represents the service options allowed for the user.

For example, when the HSGW uses the subscriber QoS profile configuration process to retrieve subscriber QoS profile information on the Pi ^* reference point, the following process is performed. The HSGW processes subscriber QoS profile parameters received from the 3GPP2 AAA Proxy / Server as specified in Table 7 below. The following subscriber QoS profile parameters may be applied to the 3GPP2 access network.

Maximum Authorized Aggregate Bandwidth for Best-Effort Traffic

Authorized Flow Profile IDs for Each Direction

Maximum per Flow Priority

Service Option Profile

Inter-User Priority for Best-Effort Traffic

3GPP2 Access Network QoS Parameters Explanation Maximum permitted aggregate bandwidth for optimally efficient traffic It is set to the value of Maximum-Authorized-Aggregate-Bandwidth-for Best-Effort-Traffic AVP received from 3GPP2 AAA.
The HSGW forwards the maximum allowed aggregated bandwidth parameters to eAN / ePCF for optimal efficiency traffic via A11-session update messages when possible. Permitted flow profile ID for each direction It is set to the value of Authorized-Flow-Profile-ID-for-the-User AVP received from the 3GPP2 AAA proxy / server.
The HSGW forwards the Permitted Flow Profile ID parameter for each direction to eAN / ePCF via A11-session update message if possible. Max flow priority It is set to the value of Maximum-Per-Flow-Priority-for-the-User AVP received from the 3GPP2 AAA proxy / server.
The HSGW forwards the maximum flow priority parameter to the eAN / ePCF via an A11-session update message if possible. Service option profile Set to the value of Service-Option-Profile AVP received from the 3GPP2 AAA Proxy / Server.
The HSGW forwards the service option profile parameters to the eAN / ePCF via A11-session update message if possible. Priority within users for optimally efficient traffic It is set to the value of Inter-User-Priority AVP received from 3GPP2 AAA Proxy / Server.
The HSGW forwards the priority parameters in the user to eAN / ePCF for optimal efficiency traffic via A11-session update messages when possible.

8 is a flowchart illustrating a process 800 of wireless communication. At 802, a QoS profile is configured. At 804, a QoS profile request message is received on the first wireless network. At 806, a QoS profile response message is sent on the first wireless network. As an example, a list of supported-feature distributed value pairs (AVPs) may also be received. If all AVPs in the received list are supported, a complete set of supported characteristics may be included in the QoS profile response message.

As an example, process 800 may be implemented in 3GPP2 AAA proxy server 318 when the first network is a 3GPP2 network. The 3GPP2 AAA proxy server 318 is also operable in a second wireless communication system implementing a second wireless protocol (eg 3GPP) and interfaces with an AAA server that authenticates subscriber devices in the first wireless communication system. )can do.

9 is a block diagram illustrating a portion of a wireless communication device 900. Module 902 is for configuring a QoS profile. Module 904 is for receiving a QoS profile request message on a first wireless network. Module 906 is for sending a QoS profile response message on the first wireless network. Apparatus 900 and modules 902, 904, and 906 may further implement various techniques described herein.

10 is a flowchart illustrating a process 1000 of wireless communication. At 1002, a QoS profile request command is sent. At 1004, a QoS profile response message is received that includes the result code. At 1006, a QoS profile configuration action is performed in response to the result code. For example, the process may be performed at the HSGW 310.

11 is a block diagram illustrating a part of the wireless communication device 1100. Module 1102 is for sending a QoS profile request command. Module 1104 is for receiving a QoS profile response message containing a result code. Module 1106 is for performing a QoS profile configuration action in response to the result code. The apparatus 1100 and modules 1102, 1104, 1106 may further implement various techniques described herein.

12 is a flow diagram illustrating a process 1200 of wireless communication that enables both an evolved universal terrestrial radio access network (E-UTRAN) connection and a cdma2000 evolved high rate packet data (eHRPD) connection. At 1202, data of a 3GPP2 subscriber QoS profile in a 3rd generation partnership project 2 (3GPP2) authentication, authorization and accounting (AAA) proxy / server is provided. At 1204, an evolved high rate packet data (eHRPD) serving gateway (HSGW) is provided that is operable to request information about the subscribed user's subscriber QoS profile from the 3GPP2 AAA proxy / server after successful authentication of the subscribed user. At 1206, a 3GPP2 AAA proxy / server is provided that is operative to send information about the requested subscriber QoS profile to the HSGW.

FIG. 13 is a block diagram illustrating a portion of a wireless communication system 1300 that enables wireless communication having both an evolved universal terrestrial radio access network (E-UTRAN) connection and a cdma2000 evolved high rate packet data (eHRPD) connection. Module 1302 is for providing data of 3GPP2 subscriber QoS profiles in 3rd generation partnership project 2 (3GPP2) authentication, authorization and accounting (AAA) proxies / servers. Module 1304 is for providing an evolved high rate packet data (eHRPD) serving gateway (HSGW) that is operable to request information about the subscribed user's subscriber QoS profile from the 3GPP2 AAA proxy / server after successful authentication of the subscribed user. The 3GPP2 AAA Proxy / Server is operable to send information about the requested subscriber QoS profile to the HSGW.

14 is a flow diagram illustrating a process 1400 of wireless communication. At 1402, data of a 3GPP2 subscriber QoS profile in a third generation partnership project (3GPP) authentication, authorization and accounting (AAA) / home subscriber server (HSS) is provided. At 1404, after successful authentication of the subscribed user, the data of the subscribed user's 3GPP2 subscriber QoS profile is directed from the 3GPP AAA / HSS to the evolved high rate packet data (eHRPD) serving gateway (HSGW). A 3GPP2 AAA proxy / server is operated that sends the subscriber QoS profile requested at 1406 to the HSGW.

FIG. 15 is a block diagram illustrating a portion of a wireless communication system 1500 that provides wireless communication with both an E-UTRAN connection and a cdma2000 eHRPD connection. Module 1502 is for providing data of 3GPP2 subscriber QoS profile in 3rd generation partnership project 2 (3GPP2) authentication, authorization and accounting (AAA) / home subscriber server (HSS). Module 1504 is for guiding the subscribed user's 3GPP2 subscriber QoS profile data from the 3GPP AAA / HSS to the evolved high rate packet data (eHRPD) serving gateway (HSGW) after successful authentication of the subscribed user. Module 1506 is for operating a 3GPP2 AAA proxy / server that sends the requested subscriber QoS profile to the HSGW.

Embodiments, modules, and functional operations described herein include digital electronic circuitry or computer software that includes the structures described herein, their structural equivalents, or a combination of one or more thereof. It may be implemented in software, firmware or hardware. The described embodiments can be implemented as one or more computer program products. One or more computer program products represent one or more modules of computer program instructions encoded on a computer readable medium for performing by a data processing device or controlling the operation of the data processing device. Computer-readable media affects machine-readable storage devices, machine-readable storage substrates, memory devices, and machine-readable propagated signals It can be a combination of substances or one or more of them. The term “data processing device” encompasses all devices and machines for data processing, including, for example, a programmable processor, a computer, or a form of a plurality of processors or computers. The apparatus may include hardware as well as code that creates an execution environment for the computer program under discussion. For example, the code may comprise processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of these. A propagated signal is a signal artificially generated by encoding information for transmission suitable for a receiving device. For example, electrical, optical and electromagnetic signals generated by machines.

Computer programs (or programs, software, software applications, scripts or code) may be written in any form of programming language, including compiled or interpreted languages. In addition, the computer program may be installed in any form including a standalone program or module, component, subroutine or other suitable unit for use in a computing environment. The computer program need not correspond to a file in the file system. A program may be stored in a markup language document or other program or data in a single file or a plurality of coordinated files (files that store one or more modules, subprograms or portions of code) dedicated to the program under discussion. One or more scripts). The computer program may be installed to be executed on one computer or a plurality of computers that are located in one place or a plurality of distributed places and connected to each other by a communication network.

The processes and logic flows described herein may be performed by one or more programmable processors executing one or more computer programs that operate on input data and generate output to perform functions. Processes and logic flows may also be performed by special purpose logic circuitry, such as field programmable gate arrays (FPGAs) or application specific integrated circuits (ASICs), and apparatus may also be implemented thereby.

Processors suitable for the execution of computer programs include, for example, both general and special purpose processors and one or more processors of any kind of digital computer. In general, a processor receives instructions and data from read only memory (ROM) or random access memory (RAM) or both. An essential element of a computer is a processor that performs instructions and one or more memory devices that store instructions and data. In general, a computer also includes or is operatively connected to one or more mass storage devices that receive data, transmit data, or store data, such as magnetic optical disks or optical disks, for all. However, computers do not necessarily need these devices. Computer-readable media suitable for storing computer program instructions and data can be any of the following types: magnetic disks, such as EPROMs, EEPROMs, flash memory devices, internal hard disks or removable disks, magnetic optical disks, CD ROMs, and DVD-ROM disks. Non-volatile memory, media, and memory devices. The processor and memory can be supplemented by or included in special purpose logic circuitry.

Although this specification contains many details, it is not to be construed as limiting the scope of the claimed or claimed invention, but may be construed as describing the characteristics of a particular embodiment. Certain features that are described in the context of different embodiments within this specification may be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may be implemented within a plurality of embodiments or any suitable sub-combination separated from each other. In addition, although a feature described above is described as a particular combination, and one or more features from the claimed combination are deleted from the combination for the first time, the claimed combination may be indicated as a subcombination or a variant of the subcombination. Similarly, although the operations in the figures are drawn in a particular order, this cannot be understood to require that such operations be performed or that all operations shown be performed in the specific order or sequential order shown in the drawings in order to obtain the desired result.

Only a few examples or implementations are described herein. Modifications, modifications, and enhancements to the examples and implementations described may be added based on what is described.

Claims (20)

A wireless communication device operating in a first wireless communication system implementing a first wireless communications protocol,
A subscriber QoS profile module for constructing a quality of service (QoS) profile;
A receiving module for receiving a QoS profile request message on the first wireless network; And
And a sending module for sending a QoS profile response message over the first wireless network. The method of claim 1,
The receiving module is further configured to receive a list of supported-features attribute-value pairs (AVPs),
The transmitting module is further configured to include in the QoS profile response message a complete set of features supported when all AVPs in the received list are supported. The method of claim 1,
The receiving module is further configured to receive a list of support characteristic attribute-value pairs (AVPs),
The sending module, when not all AVPs in the received list are supported, includes a complete set of supported characteristics in the QoS profile response message and includes an Experimental-Result-Code AVP set to DIAMETER_ERROR_FEATURE_UNSPPORTED. It is further configured to include a wireless communication device. The method of claim 1,
The receiving module is further configured to receive a list of support characteristic attribute-value pairs (AVPs),
And wherein the sending module is further configured to include a list of received AVPs and an indication of failure in the QoS profile response message when the list of supported characteristic AVPs is not supported. The method of claim 1,
Operable in a second wireless communication system implementing a second wireless communication protocol, wherein authentication, authorization and accounting for authentication of subscriber equipment to the first wireless communication system (AAA) server further comprises an interface module (interface module) for connecting. A wireless communication method implemented in a first wireless communication system implementing a first wireless communications protocol,
Configure a quality of service (QoS) profile,
Receive a QoS profile request message on the first wireless network,
Sending a QoS profile response message over the first wireless network. A wireless communication device constituting a subscriber quality of service (QoS) profile, comprising:
A sending module for sending a QoS profile request command;
A receiving module for receiving a QoS profile response message including a result code; And
A configuration module for performing a QoS profile configuration action in response to the result code. The method of claim 7, wherein
The configuration module,
When the received result code indicates an unsupported feature error, the subscriber QoS profile configuration is stopped,
And when the received result code indicates success, process the received QoS parameters in the QoS profile response message according to a predetermined procedure. A method of configuring a subscriber quality of service (QoS) profile in a wireless network, the method comprising:
Send a QoS profile request command,
Receive a QoS profile response message containing a result code,
Performing a QoS profile configuration action in response to the result code. The method of claim 9,
When the received result code indicates a characteristic error that is not supported, the subscriber QoS profile configuration is stopped,
Processing the received QoS parameters in the QoS profile response message according to a predetermined procedure when the received result code indicates success. A method of enabling wireless communication having an evolved universal terrestrial radio access network (E-UTRAN) connection and a cdma2000 evolved high rate packet data (eHRPD) connection,
Provide data of 3GPP2 subscriber QoS profiles in 3rd generation partnership project 2 (3GPP2) authentication, authorization and accounting (AAA) proxies / servers,
After successful authentication of a subscribed user, providing an evolved high rate packet data (eHRPD) serving gateway (HSGW) operable to request information about the subscribed user's subscriber QoS profile from the 3GPP2 AAA proxy / server,
Providing the 3GPP2 AAA proxy / server operative to send information about the requested subscriber QoS profile to the HSGW. The method of claim 11,
And using an enhanced communication protocol between the HSGW and the 3GPP2 AAA proxy / server to support subscriber QoS profile parameters. The method of claim 12,
Information on the requested subscriber QoS profile is communicated to the HSGW without using a policy and charging control (PCC) function. A system for enabling wireless communication having an evolved universal terrestrial radio access network (E-UTRAN) connection and a cdma2000 evolved high rate packet data (eHRPD) connection,
A first module for providing data of a 3GPP2 subscriber QoS profile in a 3rd generation partnership project 2 (3GPP2) authentication, authorization, and accounting (AAA) proxy / server;
A second module providing an evolved high rate packet data (eHRPD) serving gateway (HSGW) operable to request information about the subscriber QoS profile of the subscribed user from the 3GPP2 AAA proxy / server after successful authentication of the subscribed user Including,
The 3GPP2 AAA proxy / server is operative to send information about the requested subscriber QoS profile to the HSGW. 15. The method of claim 14,
And a third module that uses an enhanced communication protocol between the HSGW and the 3GPP2 AAA proxy / server to support subscriber QoS profile parameters. 15. The method of claim 14,
And wherein the information about the requested subscriber QoS profile is delivered to the HSGW without using a policy and charging control (PCC) function. A method for providing wireless communication having an evolved universal terrestrial radio access network (E-UTRAN) connection and a cdma2000 evolved high rate packet data (eHRPD) connection,
Provide data of 3GPP2 subscriber QoS profiles in 3rd generation partnership project (3GPP) authentication, authorization and accounting (AAA) / home subscriber servers (HSS),
After successful authentication of the subscribed user, the data of the subscribed user's 3GPP2 subscriber QoS profile is directed from the 3GPP AAA / HSS to an evolved high rate packet data (eHRPD) serving gateway (HSGW),
Operating a 3GPP2 AAA proxy / server that sends the requested subscriber QoS profile to the HSGW. The method of claim 17,
Information on the requested subscriber QoS profile is communicated to the HSGW without using a policy and charging control (PCC) function. A system for providing wireless communication having an evolved universal terrestrial radio access network (E-UTRAN) connection and a cdma2000 evolved high rate packet data (eHRPD) connection,
A first module for providing data of a 3GPP2 subscriber QoS profile in a 3rd generation partnership project (3GPP) authentication, authorization, and accounting (AAA) / home subscriber server (HSS);
A second module for guiding data of the subscribed user's 3GPP2 subscriber QoS profile from the 3GPP AAA / HSS to an evolved high rate packet data (eHRPD) serving gateway (HSGW) after successful authentication of the subscribed user; And
And a third module operating a 3GPP2 AAA proxy / server that sends the requested subscriber QoS profile to the HSGW. The method of claim 19,
Information on the requested subscriber QoS profile is communicated to the HSGW without using a policy and charging control (PCC) function.

Images