Enhanced qos control

TECHNICAL FIELD

0001[0001] The present invention relates to wireless communications. In particular, the present invention relates to control of the Quality of Service (QoS) for wireless communications.

BACKGROUND ART

0002[0002] Conventional wireless communication networks suffer from the problem of static, limited traffic classification capability. <figref idref="f0001">Fig. 1</figref> shows a network having a plurality of application provider networks (APNs) 100-1 to 100-n connected to a Gateway GPRS Service Node (GGSN) 440 through respective QoS controls 110-1 to 110-n. Communication services are provided to terminals 160 through corresponding radio access networks 150 and Service GPRS Service Nodes 130. The radio access networks 150 may be R99 compliant GPRS networks including a base station system or 3GPP R99/R4 compliant WCDMA radio access networks. A Home Location Register (HLR) 140 contains one QoS profile for each APN 100.

0003[0003] At least some of terminals 160 are likely to be unable to make any QoS request, or to make a QoS request for different communication services. Thus, the communications services cannot depend on a traffic class based classification from the terminals 160. Instead, the network applies the same HLR based QoS control for all services provided by a single APN and is not able to give differentiated treatment for Wireless Application Protocol (WAP) browsing and Multimedia Media Messaging Service (MMS) from the same APN even if HLR 140 can set the maximum QoS profile per traffic class. Such a static HLR based control is not service-aware and has disadvantages. It is not possible to achieve differentiated treatment for different types of service usage within one traffic class and the network is sufficient only for short-term simple communication services.

0004<patcit id="pcit0001" dnum="US20020036983A"><text>US 2002/0036983</text></patcit> discloses a method of filtering and gating data flow in a QoS connection between a remote host and user equipment in a packet data network using policy control mechanisms includes a remote host initiating an application in an application server and a corresponding session between the remote host and the user equipment ("UE") via the application server. The UE requests, to a gateway support node ("GGSN") of the network, establishment of a network bearer service between the UE and the remote host. A corresponding policy control function ("PCF") in a policy server receives, from the application server, filtering data derived from session data received by the application server during the session.

0005<patcit id="pcit0002" dnum="US20020062379A"><text>US 2002/0062379</text></patcit> discloses method and apparatus for coordinating quality of service requirements for media flows in a multimedia session with IP bearer services. To set up a multimedia session involving a mobile terminal, a session packet access bearer is established between the mobile terminal and an access point to a packet data network by way of a radio access network. The access point is coupled to a multimedia system that provides multimedia session services. Using the session packet access bearer, a multimedia session involving the mobile terminal is initiated that includes a plurality of media data streams.

0006The 3^rd Generation Partnership Project (3GPP) has attempted to provide for policy based admission control in Release 5 of their specifications. See www.3gpp.org. This specification includes a Policy Control Function (PCF), which although a separate logical entity from the Proxy Connection State Control Function (P-CSCF), is described as being a physical part of the P-CSCF in Release 5. <figref idref="f0002">Fig. 2</figref> illustrates the implementation of the PCF as part of the P-CSCF 180. Consequently, policy based admission control is only available for communication services provided through the IP multimedia subsystem and only the IP multimedia subsystem may request resources of the radio access network (for example, GSM or UMTS) for the communication services. The Gateway GPRS Service Node (GGSN) 440 initiates policy requests at packet data protocol (PDP) context activation or modification. For QoS control of a PDP context, the PCF of the P-CSCF/Policy Control Function 180 sends an indication of the maximum allowable QoS to the GGSN 440, and the GGSN then sets a QoS (no higher than the maximum allowable QoS) for the PDP context.

0007The 3GPP TS 23.207 (V5.50 (2002-09) and TS 29.207 V5.1.0 (2002-09) describe the function of the PCF.

0008The policy control procedure of 3GPP Release 5 of the PCF is described in more detail in <figref idref="f0003">Fig. 3</figref>. This policy control procedure comprises the following six steps: <ol id="ol0001" compact="compact"><li>1. A SIP message containing SDP payload is received by the P-CSCF 210. The Session Description Protocol (SDP) payload includes the session QoS related information such as media type and bit rate.</li><li>2. The PCF 220 is a decision point and authorizes the required QoS resources for the session and installs the IP bearer level policy based on information from the P-CSCF 210. The PCF 220 generates an authorization token and sends the token to the P-CSCF 210. Upon successful authorization of the session, the P-CSCF 210 forwards (the methodology is not illustrated, but is well known) the SDP payload to the UE 160 for the originating side, with the authorization token.</li><li>3. The UE 160 sends an Activate (Secondary) PDP Context Request to the SGSN 130 with the UMTS QoS parameters. The UE 160 includes the Binding Information (authentication token and flow IDs) in the Activate PDP Context Request. The SGSN 130 sends the corresponding Create PDP Context</li></ol> Request to the GGSN 440.

0009The GGSN 440 sends a Common Open Policy Service Protocol (COPS) protocol REQ message with the Binding Information to the PCF 220 in order to obtain relevant policy information. The message includes a token and flow identification(s). <ul id="ul0001" list-style="none" compact="compact"><li>5. The PCF 220 sends a COPS decision (DEC) message back to the GGSN 440. A DEC message from the PCF 220 to the GGSN 440 contains decision objects. A Decision object shall include one of the following commands: <ul id="ul0002" list-style="bullet" compact="compact"><li>NULL Decision (No configuration data available)</li><li>Install (Admit request/Install configuration, Commit)</li><li>Remove (Remove request/Remove configuration)</li><li>These commands are used to: (a) Authorize QoS/Revoke QoS authorization for one or more IP flows (b) Control forwarding for one or more IP flows</li></ul></li><li>6. The GGSN 440 maps IP flow based policy information into PDP context based policy information and uses the PDP context based policy information to accept the PDP activation request, and sends a Create PDP Context Response message back to SGSN 130. The SGSN 130 sends an Activate (Secondary) PDP Context Accept to UE 160.</li></ul>

0010[0007] The 3^rd Generation Partnership Project (3GPP) is currently developing Release 6 of their specifications, including enhanced policy based admission control. It has been proposed to separate the PCF 220 from P-CSCF 210 so that services other than those provided through the IP multimedia subsystem could benefit from the policy based admission control.

0011The present invention provides a method comprising: receiving, at a policy decision entity, subscriber information from a database, the subscriber information regarding permitted conditions for users to obtain services; receiving a request for a session; forming policy rules, at the policy decision entity, based upon the subscriber information and/or service information; and providing the policy rules to a policy enforcement entity to enforce at least one characteristic of the session upon a communication network.

0012The policy decision entity may be a policy control function. The policy enforcement entity may be a Gateway General Packet Radio Access Node (GGSN). The subscriber information may comprise allowed services which may be provided to the user equipment by the at least one network or server. The allowed services may be defined by a service name, a quality of service class and a bit rate at which the requested session is provided to the requesting user equipment by the at least one network or server. The subscriber information may comprise allowed services which may be provided to the user equipment by the at least one network or server. The list of services may include a service name, quality of service class and an allowed bit rate is processed by the policy decision entity as part of forming the policy rules. The service information may comprise quality of service information. The quality of service information may comprise bandwidth. The service information may comprise quality of service information. The policy rules may be default policy rules when the subscriber information is not available which is not dependent upon information the varies with different subscribers. The communications may be a packet switched network.

0013The present invention further provides a system for controlling the providing of services to user equipment comprising: a communication system including a database storing subscriber information regarding subscription of users of the user equipment to obtain sessions of the services, a policy enforcement entity to which the user equipment is coupled to obtain the services, and a policy decision entity which is coupled to the policy enforcement entity and to the database; and at least one network or server which is coupled to the policy decision entity that provides the sessions of the services to the user equipment under control of the policy decision entity; and wherein the database is configured to provide the stored subscriber information to the policy decision entity regarding subscription of the users of the user equipment to obtain the sessions of the services provided by the at least one network or server, the policy decision entity is configured to formulate policy rules defining characteristics of the sessions and/or service which may be obtained by users of the user equipment from the at least one network or server in response to the subscriber information and/or service information and the policy enforcement entity is configured to enforce in response to the policy rules the obtaining of the sessions of the services by the user equipment through the wireless system in accordance with at least one characteristic.

0014The policy decision entity may be a policy control function. The policy enforcement entity may be a Gateway General Packet Radio Access Node (GGSN). The characteristics may comprise a name of service, quality of service and a bit rate of the session to be provided to a requesting user equipment. The subscriber information may comprise allowed services which may be provided to the user equipment. The allowed services may be defined by information including a service name, a quality of service class and a bit rate at which the requested session is provided to the requesting user equipment. The service information may comprise quality of service information. The sessions may be provided by a packet switched network.

0015Additionally, the present invention provides an apparatus, comprising: means for receiving subscriber information from a database, the subscriber information regarding permitted conditions for users to obtain services; means for receiving a request for a session; means for determining characteristics of the session and/or services to be provided to user equipment; means for forming policy rules based upon the subscriber information and/or service information; and means for providing the policy rules to a policy enforcement entity to enforce at least one characteristic of the session upon a communications network. The present invention further provides a computer program embodied on a computer-readable medium, the computer program configured to control a processor to perform operations comprising: receiving, at a policy decision entity, subscriber information from a database, the subscriber information regarding permitted conditions for users to obtain services; receiving a request for a session; forming policy rules, at the policy decision entity, based upon the subscriber information and/or service information; and providing the policy rules to a policy enforcement entity to enforce at least one characteristic of the session upon a communication network.

BRIEF DESCRIPTION OF THE DRAWINGS

0016[0001] <figref idref="f0001">Fig. 1</figref> illustrates QoS control problems in a prior art wireless communication network.

0017[0002] <figref idref="f0002">Fig. 2</figref> illustrates the implementation of a policy control function in a prior art wireless communication network according to 3GPP Release 5.

0018[0003] <figref idref="f0003">Fig. 3</figref> illustrates a detailed flow diagram of the prior art policy control control procedure of 3GPP Release 5.

0019[0004] <figref idref="f0004">Fig. 4</figref> illustrates an embodiment of network controlled QoS in accordance with the invention providing different exemplary communication services.

0020[0005] <figref idref="f0005">Fig. 5</figref> illustrates an embodiment of the invention enabling operators to dynamically allocate QoS according to service need and business potential.

0021[0006] <figref idref="f0006">Fig. 6</figref> describes the control procedure for a primary PDP context setup when the user equipment has not established any communication with at least one network or server providing services.

0022[0007] <figref idref="f0007">Fig. 7</figref> illustrates the control procedure of a detected new flow in an existing PDP context.

0023<figref idref="f0008">Fig. 8</figref> illustrates the control procedure when the PCF and a service logic associated with a network or server providing services exchange information prior to applying and/or updating policy.

0024<figref idref="f0009">Fig. 9</figref> is an example of the invention enabling QoS control over a streaming communication service.

0025<figref idref="f0010">Fig. 10</figref> illustrates the process of obtaining information from the subscription manager database which is used to define a quality of service provided to a requesting user equipment.

0026Like reference numerals identify like parts throughout the drawings.

BEST MODE FOR CARRYING OUT THE INVENTION

0027This invention provides policy based admission QoS control of different networks or servers providing services. An embodiment 250 of implementation of the policy based admission QoS control in accordance with the invention is illustrated in <figref idref="f0004">Fig. 4</figref>. Unlike the prior art network illustrated in <figref idref="f0001">Fig. 1</figref>, the fully network controlled QoS in <figref idref="f0004">Fig. 4</figref> provides separate QoS controls for a collective group 260 of networks or servers in a packet switched network even if individual networks or servers 100 are provided from the same operator. The network or servers 100 are either service provider networks or service provider servers of diverse designs. The QoS controls 110 are preferably enabled within one APN operator making offering multimedia service combinations simple, terminal realizations simple, and providing consistent treatment of the same service over all of the vendor's terminals. Preferably, the QoS controls 110 can be hidden from the end user, are always linked to the offered services and are always part of the user service selection and the user receives what was purchased.

0028[0024] An embodiment 400 of the invention, which enables operators to dynamically allocate QoS according to service need and business potential, is illustrated in <figref idref="f0005">Fig. 5</figref>. Subscription Manager Database 420 is connected to PCF 405 which functions as the policy decision point/entity. The PCF 405 may be in accordance with the 3GPP TS which are referred to above. The PCF 405 decides what QoS treatment to allocate, binding of service and PDP context. From the subscription manager database 420, PCF 405 receives subscriber information, which may include subscriber specific information networks or servers 100 providing services to the UE 160, to which the subscriber subscribes to obtain access (for example, streaming services with a maximum bandwidth "X") to the services. The service logic 410 provides service information from the networks or servers 100, including the identification of services and QoS to PCF 405. The PCF 405 formulates policy rules based upon the subscriber and subscription information provided from the subscription manager database 420 and the service information provided from the at least one network or servers 100 providing service to the UE 160 and/or from the service logic 410. The local rules repository 425 stores default policy information in the form of decision logic. If the subscriber information is somehow absent from the subscription manager database420, default policy rules may be applied. The default policy rules do not vary in dependence upon different customers requesting service.

0029[0025] Preferably, the GGSN 440 initiates policy based admission control by sending a request to the PCF 405. This may happen either at PDP context activation, at PDP context modification, or when the GGSN 440 notices that a new flow is introduced in the user plane. In order to identify a new flow in the user plane, the GGSN 440 stores information on existing flows, such as source and destination IP addresses, source and destination ports, and protocol. The GGSN 440 also may filter user plane traffic and understand when user plane traffic does not match any of the existing flows.

0030[0026] The PCF 405 receives a request from the GGSN 440 and decides what QoS treatment to allocate to the PDP context or flow. For the decision, the PCF 405 may use service/QoS information received from the service logic 410 (for example, service logic 1 associated with the P-CSCF 210) involving for example, the outcome of a SDP negotiation), subscriber specific information received from the subscription manager database 420 and static information configured in the PCF 405 (for example, priority of streaming traffic in the operator's network). Any or all of this information may be stored in local repository 425 of the PCF 405. The PCF 405 also provides binding of service and PDP context.

0031[0027] The PCF 405 sends a decision on the QoS treatment to the GGSN 440. The QoS treatment may include maximum values for QoS attributes or target values for QoS attributes. The GGSN 440 functions as the policy enforcement point entity in the wireless network (not illustrated) which provides connectivity to the UE 160. The GGSN 440 enforces the QoS policy treatment decision based upon the policy rules set by the PCF received from PCF 405. Based on the treatment decision, the GGSN 440 may downgrade or upgrade the QoS requested for the PDP context or flow.

0032[0028] Policy control examples of the invention are described in conjunction with <figref idref="f0006 f0007 f0008">Figs. 6-8</figref>. <figref idref="f0006">Fig. 6</figref> illustrates the control procedure for a primary PDP context setup where the user has not yet established any communication with a service provider network or server 100; <figref idref="f0007">Fig. 7</figref> illustrates the control procedure for a detected new flow in the existing PDP context; and <figref idref="f0008">Fig. 8</figref> describes the control procedure when the PCF 405 and the service logic 410 exchange information prior to applying and/or updating.

0033[0029] The control procedure of <figref idref="f0006">Fig. 6</figref> has six steps: <ol id="ol0002" compact="compact"><li>1. The UE 160 sends an Activate (primary) PDP Context message to the SGSN 130 with the UMTS QoS parameters. The SGSN 130 validates the request against PDP context subscription records earlier received from the HLR (not illustrated in <figref idref="f0006">Fig. 6</figref>, but may be in accordance with <figref idref="f0001">Fig. 1</figref>). The SGSN 130 may downgrade the QoS Requested. The SGSN 130 sends the corresponding Create PDP Context message to the GGSN 440.</li><li>2. The GGSN 440 sends a COPS REQ message with the Binding Information to the PCF 400 in order to obtain relevant policy information. The binding information used here includes the Subscriber identity (IMSI) and the accessed Access Point Name (APN). In the backbone network of the wireless system, the APN is a reference to the GGSN to be used. In addition the APN may, in the GGSN, identify the network or server 100 to be used to provide service to the UE 160 and optionally, a service to be offered. APN as defined in 3GPP TS 23.003, is described as follows: <ul id="ul0003" list-style="none" compact="compact"><li>The APN Network Identifier is mandatory and is a label (for example "corporation" or "service") or a set of labels separated by dots, which is a fully qualified domain name according to the DNS naming conventions (for example "company.com" or "service.company.com"). In order to guarantee the uniqueness of the APN, the packet-domain public land mobile network should allocate, to an ISP or corporation, an APN Network Identifier identical to their domain name in the public Internet. The APN Network Identifier shall not end with ".gprs". An APN Network Identifier of 3 or more labels and that starts with a Reserved Service Label, or an APN Network Identifier that consists of a Reserved Service Label alone, indicates that for the APN a GGSN supports additional services such as external PDN address allocation or Mobile IP support. Reserved Service Labels, e.g., "dhcp"or "MIPv4FA", and the corresponding services that they stand for, e.g., external PDN address allocation via DHCP, or Mobile IP Foreign Agent support, are to be agreed upon among operators.</li><li>The APN Operator Identifier is optional. It is a fully qualified domain name according to the DNS naming conventions, and consists of three labels.</li><li>The APN Operator Identifier shall end in ".gprs". For example, it may be "MNCyyy.MCCzzzz.gprs". The exact format is defined in 3G TS 29.060. The APN stored in the HLR shall not contain the APN Operator Identifier. A wild card may be stored in the HLR instead of the APN. This wild card indicates that the user may select an APN that is not stored in the HLR.</li><li>The use of the wild card is described in Annex A.</li></ul></li><li>3. The PCF 400 may retrieve subscription data from the Subscription Manager Database 420, if the information is not already present locally in the local rules repository 425. It should be noted that the subscription data represents information about each subscription that a subscriber has for receiving service sessions from the APNs 100 as illustrated for example in <figref idref="f0005">Fig. 5</figref>. Each subscriber, who is a user of the UE 160, may have multiple subscriptions each defining different service parameters. The PCF 405 uses the Subscriber identity provided by the GGSN 440 for this purpose. Additionally, PCF 405 may also use the accessed network or server 100 to search for more specific subscription data.</li><li>4. The subscription data stored in the Subscription Manager Database 420 includes for each subscription allowed services for the given subscriber, and QoS class and bitrate information.</li><li>5. Based on subscription information, as well as the rules stored locally in the local rules repository 425 of the PCF 405, the PCF makes the treatment decision to be allocated. The PCF 405 sends a COPS DEC message back to the GGSN 440. A Decision (DEC) message from the PCF 405 to the GGSN 440 contains decision objects. A Decision object includes the PDP context QoS class and bit rates, a list of allowed services to be carried by the PDP context, and the QoS class and bit rates for each service.</li><li>6. The GGSN 440 uses the PDP context based policy information to accept the PDP activation request, and sends a Create PDP Context Response message back to SGSN 130. The GGSN 440 may propose new UMTS QoS attributes, based on the policy decision. The SGSN 130 sends an Activate (Secondary) PDP Context Accept message to UE 160.</li></ol>

0034[0030] The procedure of <figref idref="f0007">Fig. 7</figref> has three steps: <ol id="ol0003" compact="compact"><li>1. The GGSN 440 detects a new flow from UE 160 in the user plane of an ongoing PDP context that requires policy control.. To make this happen, the GGSN 440 contains the pre-configured information of classifiers which, for example, are source and destination IP addresses, source and destination ports, and protocol.</li><li>2. The GGSN 440 associates the flow with the service which is described by the service name. The GGSN 440 sends a COPS REQ message with the Binding Information to the PCF 405 in order to obtain relevant policy information used for formulating the policy rules. The binding information used here includes the service name and/or the classifier.</li><li>3. Based on subscription information, the policy rules stored locally in the local repository 430 in the PCF 405, and the communication with the relevant Service Provider Networks 100 prior to this point of time, the PCF makes a new treatment decision to be allocated. The PCF 405 sends a COPS DEC message back to the GGSN 440. The GGSN 440 enforces the authorization decision and may modify the QoS requested for the PDP context or flow.</li></ol>

0035[0031] The procedure of <figref idref="f0008">Fig. 8</figref> has six steps : <ol id="ol0004" compact="compact"><li>1. The PCF 405 receives, such as through service logic 410 associated with P-CSCF 210 of <figref idref="f0005">Fig. 5</figref>, the QoS related information (for example, media type and bit rate) of a service provided to the UE from the particular network or server (not illustrated).</li><li>2. The PCF 405 authorizes the required QoS resources for the session based jointly on subscription and service information as previously described, local rules, and optionally, any default rules when applicable. For example, the PCF 405 may limit the bit rate to be used by the service. The PCF 405 generates an authorization token and sends this to the P-CSCF (not illustrated). Upon successful authorization of the session, the P-CSCF (not illustrated) forwards the SDP payload to the UE 160 for the originating side, with the authorization token.</li><li>3. The UE 160 sends an Activate (Secondary) PDP Context to the SGSN 130 with the UMTS QoS parameters. The UE 160 includes the Binding Information (authentication token and flow IDs) in the Activate PDP Context. The SGSN 130 sends the corresponding Create PDP Context to the GGSN 440.</li><li>4. The GGSN 440 sends a COPS REQ message with the Binding Information (authorization token and flow Ids) to the PCF 405 in order to obtain relevant policy information.</li><li>5. The PCF 405 binds the REQ with the policy decision. The PCF 405 sends a COPS DEC back to the GGSN 440. A Decision (DEC) from the PCF 405 to the GGSN 440 contains decision objects. A Decision object includes the PDP context QoS class and bit rates, a list of the allowed services flows to be carried by the PDP context, and the QoS class and bit rates for each service flow.</li><li>6. The GGSN 440 uses the PDP context based policy information to accept the PDP activation request, and sends a Create PDP Context Response back to SGSN 130. The SGSN 130 sends an Activate (Secondary) PDP Context Accept to UE 160.</li></ol>

0036[0032] <figref idref="f0009">Fig. 9</figref> is an example which enables QoS control over a streaming communication service. A streaming bearer PDP context request is passed between GGSN 440 and terminal160. PCF 405 functions as described above and provides binding of the streaming session with the streaming bearer PDP context, etc. The Service Logic 410 of the streaming server or RTSP proxy 100 decides what QoS information to provide based on SDP.

0037[0033] This embodiment enables QoS control on a per session basis, as well as static service subscriptions based upon policy rules determined from consideration of the subscriber information and service provider information. It also ensures that the bearer only carries authorized traffic and, for example, the user can not use the streaming bearer to carry email traffic.

0038[0034] <figref idref="f0010">Fig. 10</figref> illustrates the process of obtaining subscriber information from the subscription manager database 420 based upon the IMSI and APN provided through the PCF 405. The PCF 405 creates the PDP context class, bitrate, list of allowed services including service name which is stored in the local rules repository and passed to the GGSN 440.

0039[0035] There are numerous advantages provided by the embodiments of the invention. One single architecture can be used to control QoS allocation to all the traffic of different service usage and user service selection/subscription. QoS allocation may be combined with session QoS information dynamically. The invention enables the network to offer differentiated treatment of interactive and background traffic in a controlled and consistent manner. There is better control resolution compared to traffic class based static subscription control from a HLR, but backwards compatibility with the conventional HLR is provided. This solution also inter-works well with multi-vendor radio access networks 150, since it utilizes the UMTS QoS bearer architecture and standard PDP context negotiation procedures. This enables the QoS policy enforcement not only in the GGSN 440 but also throughout the mobile network.

0040[0036] The invention achieves the following: <ol id="ol0005" compact="compact"><li>1. Enabling differentiation: Differentiation between individual subscribers, services and providers can be achieved via admission control and QoS negotiation leading to classification of the generated traffic. The classification then results in different kind of prioritization of the traffic in the network and hence, impacts to the probability of the service maintaining best possible quality level. This architecture enables QoS differentiation based on user selected services as well as the business potentials of different services.</li><li>2. Enabling centralized policy decision functions: The key value of this invention is to enforce operator business logic, that is to enable the utilization of mobile network resource according to the business priority of different customers and services. This architecture supports a centralized policy decision function at the mobile network edge, and more specifically, enables the mapping of business importance of user traffic into relevant GPRS bearer QoS attribute(s), and consequently enable the radio access network to handle the traffic according to the right priority.</li></ol>

0041While the invention has been described in terms of its preferred embodiments, it should be understood that numerous modifications may be made. It is intended that all such modifications fall within the scope of the appended claims.