US20080095136A1

US20080095136A1 - Approach for QoS control on un-wanted service (e.g. VoIP or Multimedia) over wireless and wireless IP network

Info

Publication number: US20080095136A1
Application number: US11/585,695
Authority: US
Inventors: Chung-Zin Liu; Thomas Trayer Towle
Original assignee: Lucent Technologies Inc
Current assignee: Nokia of America Corp
Priority date: 2006-10-24
Filing date: 2006-10-24
Publication date: 2008-04-24
Also published as: US8792823B2; US20110090849A1

Abstract

An apparatus in one example has: at least one access network operatively coupled to an access and data network; and a controller in the access and packet data network, the controller determining access of data flow from the access network through the access and data network. Embodiments allow access or packet data service providers to control which types of services are allowed over their respective access and packet data networks.

Description

TECHNICAL FIELD

The invention relates generally to telecommunication systems and, more specifically, to a system that provides for QoS control on un-wanted services (e.g. VoIP or Multimedia) over wireless and wireless IP network.

BACKGROUND

Quality of Service (QoS) refers to the capability of a network to provide better service to selected network traffic over various technologies, including Frame Relay, Asynchronous Transfer Mode (ATM), Ethernet and 802.1 networks, SONET, and IP-routed networks that may use any or all of these underlying technologies. The primary goal of QoS is to provide priority including dedicated bandwidth, controlled jitter and latency (required by some real-time and interactive traffic), and improved loss characteristics. Also important is making sure that providing priority for one or more flows does not make other flows fail. QoS technologies provide the elemental building blocks that will be used for future business applications in campus, WAN, and service provider networks.
A flow can be defined in a number of ways. One common way refers to a combination of source and destination addresses, source and destination socket numbers, and the session identifier. It can also be defined more broadly as any packet from a certain application or from an incoming interface. Recent identification tools have allowed the definition of a flow to be performed more precisely (for instance, to the URL or MIME type inside an HTTP packet).
Since wireline and wireless access and packet data services independently run over IP networks, any type of service, including services owned by other service providers, are allowed over any respective access and packet data network. A provider of the respective access and packet data network thus has little or no control over QoS (Quality of Service) or charging functions for services that flow over the respective access and packet data network.
Thus, there is a need in the art for a system that provides for QoS Control on un-wanted services (e.g. VoIP or Multimedia) over Wireless and Wireless IP network.

SUMMARY

One embodiment of the present method and apparatus encompasses an apparatus. This embodiment of the apparatus may comprise: at least one access network operatively coupled to an access and data network; and a controller in the access and packet data network, the controller determining access of data flow from the access network through the access and data network.
Another embodiment of the present method and apparatus encompasses a method. This embodiment of the method may comprise: identifying an access network operatively coupled to an access and packet data network; and one of allowing or denying a flow of packet data based on the identification of the access network.

DESCRIPTION OF THE DRAWINGS

The features of the embodiments of the present method and apparatus are set forth with particularity in the appended claims. These embodiments may best be understood by reference to the following description taken in conjunction with the accompanying drawings, in the several figures of which like reference numerals identify like elements, and in which:

FIG. 1 is a general block diagram of a network for use with the present method and apparatus;

FIG. 2 is a general block diagram of an embodiment of the present method;

FIG. 3 depicts one embodiment according to the present apparatus;

FIG. 4 depicts one embodiment according to the present method;

FIG. 5 depicts another embodiment according to the present apparatus;

FIG. 6 depicts another embodiment according to the present method;

FIG. 7 depicts yet another embodiment according to the present apparatus;

FIG. 8 depicts yet another embodiment according to the present method;

FIG. 9 depicts a further embodiment according to the present apparatus;

FIG. 10 depicts a further embodiment according to the present method;

FIG. 11 depicts a another further embodiment according to the present apparatus; and

FIG. 12 depicts a another further embodiment according to the present method.

DETAILED DESCRIPTION

Since wireline and wireless access and packet data services independently run over IP networks, without any type of control by a service provider, services owned by other service providers, are allowed over access and packet data networks. Embodiments according to the present method and apparatus allow access or packet data service providers to control which types of services are allowed over their respective access and packet data network.
FIG. 1 is a representation of one implementation of a system in which access or packet data service providers have control over the types of services are allowed over their access and packet data network 104. In general a plurality of wireline and wireless access and packet data services, such as 102 and 106, may be operatively coupled to the access and packet data network 104. The access and packet data network 104 may have a controller 106 that provides for QoS control on un-wanted services over the access and packet data network 104.
FIG. 2 is a general block diagram of an embodiment of the present method. This embodiment may have the steps of: identifying an application server operatively coupled to an access and packet data network (201); and allowing or denying a flow of packet data, for example, based on the identification of the application server (202).
In the embodiments of the present method and apparatus as described below, MPLS (Multiprotocol Label Switching) is a type of network management protocol in which incoming packets are assigned, or encapsulated with, labels, and are then forwarded through the network based on the contents of the labels. Labels may be added to, swapped, or removed, as the packets move between routers. MPLS gives network operators a great deal of flexibility to divert and route traffic, whether around congestion or bottlenecks, or to take advantage of underutilized links.
UDP (User Datagram Protocol) is a communications protocol that offers a limited amount of service when messages are exchanged between computers in a network that uses the Internet Protocol (IP). UDP is an alternative to the Transmission Control Protocol (TCP) and, together with IP, is sometimes referred to as IP address/UDP. Like the Transmission Control Protocol, UDP uses the Internet Protocol to actually get a data unit (called a datagram) from one computer to another. Unlike TCP, however, UDP does not provide the service of dividing a message into packets (datagrams) and reassembling it at the other end. Specifically, UDP doesn't provide sequencing of the packets that the data arrives in. This means that the application program that uses UDP must be able to make sure that the entire message has arrived and is in the right order. Network applications that want to save processing time because they have very small data units to exchange (and therefore very little message reassembling to do) may prefer UDP to TCP.
UDP provides two services not provided by the IP layer. It provides port numbers to help distinguish different user requests and, optionally, a checksum capability to verify that the data arrived intact.
A gateway is an entity that operates above the link layer and translates, when required, the interface and protocol used by one network into those used by another distinct network. An AGW (access gateway) is a gateway that is treated like a network interface in that it is expected to exchange routing information. Typically, if it does not do so for a period of time, the route associated with the gateway is deleted.
An access network is a network that connects directly to the end user or customer. Access networks connect to the “backbone,” which is a network made up of high-speed lines between major switching points.
It is to be understood that embodiments of the present apparatus and method may encompass numerous other types of networks, gateways, communication protocols, etc.
As depicted in the FIG. 3 apparatus and the FIG. 4 method, a Static Allowed list may be provisioned in Access Gateway to block the application server in the address list. Addresses of allowed application servers may be provisioned in the allowed list. Once it is determined that a requested application is not provisioned in the access gateway, the AGW notifies the Access network and the UE to release the resource. Some drawbacks of this approach are listed as below:
Mobile to Mobile flows do not provide useful policy criteria to determine if an application should be approved or not, that is no useful information in the IP addresse, and/or UDP ports are dynamic;
Cannot support Service Controlled QoS and Charging from service layer (e.g. Flow Based Charging);
Complicated Operation, such as Difficult to provision and update policies in PDSN compared to centralized PDF; and
Less Flexibility, such as Application Service Providers needs to coordinate with Access Service providers.
In this embodiment, depicted in FIG. 3, UE1 (user equipment) 301 and UE2 302 are operatively coupled by access networks 304 and 306, respectively, to access and packet data network 308. The access and packet data network 308 may have AGW 310 and AGW 312 operatively coupled to a MPLS 314. The AGW 310 and AGW 312 may also be operatively coupled, respectively, to access network 304 and access network 306.
An ABC application server 316 may be operatively coupled to the MPLS 314 and may utilized database 318 that has a “static” allowed list in PDSN (packet data service node) for the application server 316.
The FIG. 4 method, for use in the FIG. 3 embodiment, may have the following steps: creating a IP/UDP list of at least one application server in an access gateway (401); identifying an application server that is attempting a flow of, for example, packets of data through a respective network (402); determining if the identified application server is a member of the IP/UDP list (403); one of allowing and denying the flow as a function of the identified application server being a member of the IP/UDP list (404). The IP/UDP list may contain allowed application servers in which case the flow is allowed, or the IP/UDP list may contain non-allowed application servers in which case the flow is denied.
The FIG. 5 apparatus and the FIG. 6 method depict an embodiment for Dynamic Session Control with Restricted policy in AGW.
In this embodiment, depicted in FIG. 5, UE1 501 and UE2 502 are operatively coupled by access networks 504 and 506, respectively, to access and packet data network 508. The access and packet data network 508 may have AGW 510 and AGW 512 operatively coupled to a MPLS 514. The AGW 510 and AGW 512 may also be operatively coupled, respectively, to access network 504 and access network 506.
An ABC application server 516 may be operatively coupled to the MPLS 514 and may utilized a policy decision function (PDF) 518.
Session Control with Policy Decision Function (PDF) authorizes QoS to AGW. The default policy implemented in AGW may be “Block all services until authorization from session”. The AS (Application Server) in session layer may authorize this service with UE2 IP/UDP address or other criteria.
The FIG. 6 method, for use in the FIG. 5 embodiment, may have the following steps: Retrieving UE2 IP address/UDP port to PDF in SIP SDP, assuming same sending and receiving IP address and/or UDP port (601); Authorizing, by the AS, peer to peer service for this flow identified by UE2 IP address/UDP port or other criteria (602); Recognizing peer to peer service for this service by notifying successful authorization to the AGW (603); and Enforcing policy from the PDF and only allowing the flow with authorized services and blocking other services (604).
The FIG. 7 apparatus and the FIG. 8 method depict an embodiment, when authorization is not applied for unauthorized service providers, then the AGW will block these flows as defined in a default policy.
In this embodiment, depicted in FIG. 7, UE1 701 and UE2 702 are operatively coupled by access networks 704 and 706, respectively, to access and packet data network 708. The access and packet data network 708 may have AGW 710 and AGW 712 operatively coupled to a MPLS 714. The AGW 710 and AGW 712 may also be operatively coupled, respectively, to access network 704 and access network 706.
A non-ABC application server 716 may be operatively coupled to the MPLS 714.
The FIG. 8 method, for use in the FIG. 7 embodiment, may have the following steps: Retrieving UE2 IP address/UDP port to PDF in SIP SDP, assuming same sending and receiving IP address and/or UDP port (801); Authorizing, by the AS, peer to peer service for this flow identified by UE2 IP address/UDP port or other criteria (802); Receiving no response to AGW by other service providers (803); and Not allowing service since there is no authorization from an application server (804).
The FIG. 9 apparatus and the FIG. 10 method depict an embodiment for Dynamic Session Control with an enhanced timer in the AGW.
In this embodiment, depicted in FIG. 9, UE1 901 and UE2 902 are operatively coupled by access networks 904 and 906, respectively, to access and packet data network 908. The access and packet data network 908 may have AGW 910 and AGW 912 operatively coupled to a MPLS 914. The AGW 910 and AGW 912 may also be operatively coupled, respectively, to access network 904 and access network 906.
An ABC application server 916 may be operatively coupled to the MPLS 914 and may utilized a policy decision function (PDF) 918.
This approach supports a more open policy, that is “all services are allowed”. However, a policy authorization timer is invoked for all services. For authorization, a response is expected from an Application Server and PDF owned by agreed or authorized service providers.
The FIG. 10 method, for use in the FIG. 9 embodiment, may have the following steps: Retrieving UE2 IP address/UDP port to PDF in SIP SDP, assuming same sending and receiving IP address and/or UDP port (1001); Authorizing, by the AS, peer to peer service for this flow identified by UE2 IP address/UDP port or other criteria (1002); Recognizing peer to peer service for this service by notifying successful authorization to the AGW (1003); Enforcing policy from the PDF and allowing all the flows before a timer expires (1004).
The FIG. 11 apparatus and the FIG. 12 method depict an embodiment wherein, if service is provided by unauthorized service providers, the policy timer will be expired and the resource will be release after timeout.
In this embodiment, depicted in FIG. 11, UE1 1101 and UE2 1102 are operatively coupled by access networks 1104 and 1106, respectively, to access and packet data network 1108. The access and packet data network 1108 may have AGW 1110 and AGW 1112 operatively coupled to a MPLS 1114. The AGW 1110 and AGW 1112 may also be operatively coupled, respectively, to access network 1104 and access network 1106.
A non-ABC application server 1116 may be operatively coupled to the MPLS 1114 and may utilized a policy decision function (PDF) 1118.
The FIG. 12 method, for use in the FIG. 11 embodiment, may have the following steps: Retrieving UE2 IP address/UDP port to PDF in SIP SDP, assuming same sending and receiving IP address and/or UDP port (1201); Authorizing, by the AS, peer to peer service for this flow identified by UE2 IP address/UDP port or other criteria (1202); Receiving no response to AGW by other service providers (1203): and Enforcing policy from the PDF and releasing the resource due to an expired timer for authorized response (1204).
The present apparatus in one example may comprise a plurality of components such as one or more of electronic components, hardware components, and computer software components. A number of such components may be combined or divided in the apparatus.
The present apparatus may employ at least one computer-readable signal-bearing media that may store software, firmware and/or assembly language, etc. The computer-readable signal-bearing medium may comprise magnetic, electrical, optical, biological, and/or atomic data storage mediums. For example, the computer-readable signal-bearing medium may comprise floppy disks, magnetic tapes, CD-ROMs, DVD-ROMs, hard disk drives, and electronic memories, etc. The computer-readable signal-bearing medium may also comprise a modulated carrier signal transmitted over a network comprising or coupled with the apparatus, for instance, at least one of a telephone network, a local area network (“LAN”), a wide area network (“WAN”), the Internet, and a wireless network.
The present method and apparatus are not limited to the particular details of the depicted embodiments and other modifications and applications are contemplated. Certain other changes may be made in the above-described embodiments without departing from the true spirit and scope of the present method and apparatus herein involved. It is intended, therefore, that the subject matter in the above depiction shall be interpreted as illustrative and not in a limiting sense.

Claims

1. An apparatus, comprising:

at least one access network operatively coupled to an access and data network;

an IP/UDP list of application servers that are operatively coupled to the access and data network; and

a controller in the access and packet data network, the controller determining access of data flow from the access network through the access and data network based on the application servers in the IP/UDP list.

2. The apparatus according to claim 1, wherein a plurality of access networks are operatively coupled to the access and data network.

3. A method, comprising:

identifying at least one access network operatively coupled to an access and packet data network;

forming an IP/UDP list of application servers operatively coupled to the access and packet data network; and

one of allowing or denying a flow of packet data from the access network based on the application servers in the IP/UDP list.

4. The method according to claim 3, wherein the method further comprises provisioning static allowed list to block the flow of packet data, the static allowed list being the IP/UDP list.

5. The apparatus according to claim 3, wherein a plurality of access networks are operatively coupled to the access and data network.

6. The apparatus according to claim 1, wherein the apparatus further comprises:

at least one user equipment operatively coupled to a multiprotocol label switching network;

an active gateway operatively coupled between an access network and the multiprotocol label switching network; and

at least one application server operatively coupled to the multiprotocol label switching network that utilizes a database that has a “static” allowed list in a PDSN (packet data service node) for the application server.

7. The apparatus according to claim 6, wherein the “static” allowed list is provisioned in the access gateway to block flows from the access network.

8. The apparatus according to claim 7, wherein addresses of allowed application servers are provisioned in the allowed list.

9. The apparatus according to claim 8, wherein, once it is determined that a requested application is not provisioned in the access gateway, the access gateway notifies the access network and the respective user equipment releases a respective resource.

10. The apparatus according to claim 6, wherein a plurality of access networks are operatively coupled to the multiprotocol label switching network via respective access gateways.

11. The apparatus according to claim 1, wherein the apparatus further comprises:

at least one user equipment operatively coupled to an access network;

an active gateway operatively coupled between the access network and a multiprotocol label switching network; and

an application server operatively coupled to the multiprotocol label switching network that utilizes a policy decision function for communication between the user equipment and the application server.

12. The apparatus according to claim 11, wherein a session control with the policy decision function authorizes a quality of service to the access gateway.

13. The apparatus according to claim 12, wherein the apparatus further comprises a default policy implemented in the access gateway that blocks all services until authorized.

14. The apparatus according to claim 11, wherein all services are allowed until occurrence of a timeout, and wherein the apparatus further comprises a policy authorization timer for all services.

15. The apparatus according to claim 1, wherein the apparatus further comprises:

at least one user equipment operatively coupled to an access network;

at least one application server operatively coupled to the multiprotocol label switching network that authorizes peer to peer service for a flow identified by a predetermined criteria between the user equipment and the application server.

16. The apparatus according to claim 15, wherein the multiprotocol label switching network authorizes peer to peer service for a flow identified by user equipment IP/UDP port.

17. A method, comprising:

retrieving a first user equipment IP address/UDP port to a policy decision function, assuming same sending and receiving IP address and/or UDP port;

authorizing peer to peer service for this flow identified by a predetermined criteria;

recognizing peer to peer service for this service by notifying successful authorization to an access gateway; and

enforcing policy from the policy decision function and only allowing the flow with authorized services and blocking other services.

18. The method according to claim 17, wherein the predetermined criteria comprises a second user equipment IP address/UDP port.

19. A method, comprising:

retrieving a first user equipment IP address/UDP port to a policy decision function, a sending and receiving being the same for the IP address and/or UDP port;

enforcing policy from the policy decision function and allowing all flows before a timer expires.

20. The method according to claim 19, wherein the predetermined criteria comprises a second user equipment IP address/UDP port.