EP1332632A2 - Procede et appareil pour coordonner des exigences de qualite de service pour des flux de donnees media dans une session multimedia avec des ressources de support ip - Google Patents

Procede et appareil pour coordonner des exigences de qualite de service pour des flux de donnees media dans une session multimedia avec des ressources de support ip

Info

Publication number
EP1332632A2
EP1332632A2 EP01981280A EP01981280A EP1332632A2 EP 1332632 A2 EP1332632 A2 EP 1332632A2 EP 01981280 A EP01981280 A EP 01981280A EP 01981280 A EP01981280 A EP 01981280A EP 1332632 A2 EP1332632 A2 EP 1332632A2
Authority
EP
European Patent Office
Prior art keywords
media
session
binding information
bearer
ggsn
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP01981280A
Other languages
German (de)
English (en)
Inventor
Johnson Oyama
Thian Joo Tan
Ina Birgitta Widegren
Brian Charls Williams
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US09/985,631 external-priority patent/US20020062379A1/en
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP1332632A2 publication Critical patent/EP1332632A2/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2491—Mapping quality of service [QoS] requirements between different networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1023—Media gateways
    • H04L65/103—Media gateways in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1033—Signalling gateways
    • H04L65/104—Signalling gateways in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/60—Network streaming of media packets
    • H04L65/65—Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/61—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources taking into account QoS or priority requirements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/55—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for hybrid networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/56—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for VoIP communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/57—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP for integrated multimedia messaging subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8016—Rating or billing plans; Tariff determination aspects based on quality of service [QoS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20—Technology dependant metering
    • H04M2215/202—VoIP; Packet switched telephony
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20—Technology dependant metering
    • H04M2215/204—UMTS; GPRS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/20—Technology dependant metering
    • H04M2215/208—IMS, i.e. Integrated Multimedia messaging Subsystem
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/22—Bandwidth or usage-sensitve billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/32—Involving wireless systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/44—Charging/billing arrangements for connection made over different networks, e.g. wireless and PSTN, ISDN, etc.
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/74—Rating aspects, e.g. rating parameters or tariff determination apects
    • H04M2215/7414—QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/78—Metric aspects
    • H04M2215/7833—Session based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • the present invention generally relates to Internet Protocol (IP) networks, and more specifically, to coordinating Quality of Service (QoS) provisioning mechanisms in IP networks with multimedia applications.
  • IP Internet Protocol
  • QoS Quality of Service
  • IP networks were originally designed to carry "best effort” traffic where the network makes a "best attempt” to deliver a user packet, but does not guarantee that a user packet will arrive at the destination. Because of the market success of IP networks, there is a clear requirement for mechanisms that allow IP networks to support various types of applications. Some of these applications have Quality of Service (QoS) requirements other than "best effort" service. Examples of such applications include various real time applications (EP Telephony, video conferencing), streaming services (audio or video), or high quality data services (browsing with bounded download delays). Recognizing these QoS requirements, the Internet Engineering Task Force (IETF), which is the main standards body for IP networking, standardized a set of protocols and mechanisms that enable IP network operators to build QoS-enabled IP networks.
  • QoS Quality of Service
  • Fig. 1 depicts a simplified high-level model of an IP network which may be useful in explaining QoS provisioning.
  • the model includes two users, but could easily be expanded to include more users without changing the basic functionality of the network.
  • User-A 101 may communicate with User-B 102 or with an application server 103.
  • User-A 101 may communicate with User-B 102.
  • User-A 101 may communicate with the application server 103, which may be configured as a video server.
  • User-A 101 accesses an IP backbone network 104 through a local access network 105, such as PSTN (dial-in access), Global System for Mobile Communications (GSM), or Universal Mobile Telecommunications System (UMTS) network.
  • a local access network 105 such as PSTN (dial-in access), Global System for Mobile Communications (GSM), or Universal Mobile Telecommunications System (UMTS) network.
  • User-B 102 is similarly connected to the IP network 104 through a local access network 106. It will be appreciated that User-A and User-B need not use the same type of access network.
  • the IP network 104 may consist of a number of IP routers and interconnecting links that together provide connectivity between the IP network's ingress and egress points and thereby make two party communication possible. As far as the users are concerned, the perceived QoS depends on the mechanisms both in the access networks 105, 106 and on the IP backbone network 104. Of particular interest to this invention is the specific case where at least one of the access networks is a UMTS or G
  • IP based services When users access IP based services, they typically use a device that runs an application program that provides the interface for the user to access the particular service. For instance, in Fig. 1, User-A may use a laptop running a conferencing application program to attend an IP network based meeting, where participants of the meeting collaborate using various programs. Such programs are well known in the art.
  • Various user applications may access network services through an application programming interface (API).
  • An API provides application programmers with a uniform interface to access underlying system resources. For instance, an API may be used to configure a network resource manager to require that a particular IP packet originating from a given application receive a certain treatment from the network, such as a particular QoS. For example, if the IP network is a Differentiated Services IP network, then an application program may request that all of its IP packets receive the "Expedited Forwarding" treatment.
  • the User may not be aware of the different technologies that various access networks and IP backbone networks employ in order to provide QoS end-to-end, i.e., from User-A all the way to remote User-B.
  • the application program may use an RSVP/IntServ based API, and the end-to-end embodiment in which he is involved may include a UMTS access network and a non-RSVP enabled IP network.
  • RSVP/IntServ based API may be used to provide QoS end-to-end.
  • the end-to-end embodiment in which he is involved may include a UMTS access network and a non-RSVP enabled IP network.
  • some "interworking" mechanisms between such different technologies and protocols are needed to make sure that the QoS is provided end-to-end.
  • Integrated Services provides a set of well-defined services which enables an application to choose among multiple, controlled levels of delivery service for their data packets. To support this capability, two things are required. First, individual network elements, such as subnets and IP routers, along the path followed by an application's data packets must support mechanisms to control the quality of service delivered to those packets. Second, a way to communicate the application's requirements to network elements along the path and to convey QoS management information between network elements and the application must be provided.
  • IntServ defines a number of services such as Controlled-Load (defined in IETF RFC 2211) and Guaranteed (defined in IETF RFC 2212).
  • the service definition defines the required characteristics of the network equipment in order to deliver the service.
  • the individual network elements (subnets and IP routers) that support the service must comply with the definitions defined for the service.
  • the service definition also defines the information that must be provided across the network in order to establish the service. This function may be provided in a number of ways, but it is frequently implemented by the resource reservation setup protocol RSVP (defined in IETF RFC 2205).
  • RSVP Resource reSerVation Protocol
  • the RSVP protocol is used by a host (e.g., User A's computer) to request specific service from the network for particular application data streams or flows. RSVP is also used by routers to deliver quality-of-service requests to all nodes along the path(s) of the flows and to establish and maintain the state(s) to provide the requested service. RSVP requests generally result in resources being reserved in each node along the data path.
  • Fig. 2 shows an End-to-End Integrated Service between the hosts.
  • the service is provided using routers and hosts that support the service definition defined for the required service and through signaling of the relevant information between the nodes.
  • RSVP is a protocol that is primarily designed to be end-to-end, extra functionality is required in a situation where the RSVP sender would like to use it for resource reservation only in some portion of the end-to-end path. This situation may arise if RSVP is used in an access network and over-provisioning is used in the backbone network. In such situations, an RSVP (Receiver) Proxy is useful.
  • a Proxy is a network device, such as a router or a switch, that performs one or more functions on behalf of another device.
  • An RSVP Proxy originates the RSVP RESV message in response to an incoming PATH message on behalf of the receivers) identified by the PATH message.
  • RSVP and PATH are well known messages used in RSVP.
  • the RSVP (Receiver) Proxy acts on behalf of the remote host and thereby facilitates resource reservation between the originating host and the RSVP Proxy without the host needing to be involved in RSVP signaling. This is shown in Fig. 3.
  • the RSVP Proxy may use knowledge of network conditions between the RSVP Proxy and the non-RSVP host.
  • Differentiated Services enhancements to the Internet protocol are intended to enable scalable service discrimination in the Internet without the need for per-flow state and signaling at every hop.
  • DiffServ Differentiated Services
  • a variety of services may be built from a small, well-defined set of building blocks which are deployed in network nodes.
  • the services may be either end-to-end or intra-domain; they include both those that can satisfy quantitative performance requirements (e.g., peak bandwidth) and those based on relative performance (e.g., "class” differentiation).
  • Services may be constructed by a combination of setting bits in an IP header field at network boundaries (autonomous system boundaries, internal administrative boundaries, or hosts), using those bits to determine how packets are forwarded by the nodes inside the network, and conditioning the marked packets at network boundaries in accordance with the requirements or rules of each service.
  • network boundaries autonomous system boundaries, internal administrative boundaries, or hosts
  • Differentiated Services defines an edge router at the network boundary, and core routers within the network.
  • the edge and core routers have different duties.
  • the edge router must condition the traffic to ensure that it conforms to the service agreement. It also marks the traffic with the appropriate DSCP (Differentiated Services Code Point). It then forwards the packet according to the service behavior defined for that DSCP.
  • the service behavior called the Per Hop Behavior (PHB) may define the prioritization or weighting of that traffic to give it better service than other traffic.
  • PHB Per Hop Behavior
  • the core nodes examine the DSCP and apply the service behavior appropriate for that service.
  • Fig. 4 shows an end-to-end service.
  • the DS edge routers perform the traffic conditioning, while the DS core routers simply apply the PHB.
  • Services may be constructed by a unique combination of PHB and traffic conditioning. For example, two different services can be created using the same PHB by applying a different traffic conditioning functioning at the edge routers.
  • the IntServ architecture provides a means for the delivery of end-to- end QoS to applications over heterogeneous networks.
  • the IntServ architecture must be supported over a wide variety of different types of network elements.
  • a network that supports Differentiated Services may be viewed as a network element in the total end-to-end path.
  • DiffServ regions of the network are treated as virtual links connecting IntServ capable routers or hosts (much as an ethernet LAN can be treated as a virtual link).
  • routers implement specific PHBs (aggregate traffic control). The total amount of traffic admitted into the DiffServ region that will receive a certain PHB is controlled by the conditioning at the edge routers.
  • An IntServ service can be provided across a DiffServ domain by applying admission control and traffic conditioning at the edge router to meet the IntServ Service specification, and signaling the RSVP service characteristics of the DiffServ domain to the next RSVP- enabled router. The information provided in the RSVP signaling should be appropriate for the service across the DiffServ domain. This is shown in Fig. 5.
  • a QoS bearer must be set up from the source to the destination of the service.
  • a bearer is a logical connection between two entities through one or more interfaces, networks, gateways, etc., and usually corresponds to a data stream.
  • a QoS bearer service includes all aspects to enable the provision of a contracted QoS. These aspects are among others the control signaling, user plane transport, and QoS management functionality.
  • GPRS General Packet Radio Service
  • UMTS Universal Mobile Telecommunication System
  • the GPRS/UMTS network includes a set of network elements between the host, referred to as the Mobile Station (MS), and an external packet switching network the user is connecting to like the Internet. These network elements are shown in Fig. 6.
  • the radio access network (RAN) provides access over the radio interface to/from the MS.
  • the RAN is coupled to a supporting gateway Gateway GPRS Support Node (SGSN) and a Gateway GPRS Support Node (GGSN).
  • SGSN Gateway GPRS Support Node
  • GGSN Gateway GPRS Support Node
  • the GGSN provides the interworking with external packet-switched networks.
  • a mobile host Before a mobile host can send packet data to an external host, the mobile host must "attach" to the GPRS network to make its presence known and to create a packet data protocol (PDP) context to establish a relationship with a GGSN towards the external network that the mobile host is accessing.
  • PDP packet data protocol
  • the PDP attach procedure is carried out between the mobile host and the SGSN to establish a logical link.
  • a temporary logical link identity is assigned to the mobile host.
  • a PDP context is established between the mobile host and a GGSN selected based on the name of the external network to be reached.
  • One or more application flows (sometimes called "routing contexts") may be established over a single PDP context through negotiations with the GGSN.
  • an application flow corresponds to a stream of data packets distinguishable as being associated with a particular host application.
  • An example application flow is in an electronic mail message from the mobile host to a fixed terminal.
  • Another example application flow is a link to a particular Internet Service Provider (ISP) to download a graphics file from a website.
  • ISP Internet Service Provider
  • Both of these application flows are associated with the same mobile host and the same PDP context.
  • User data is transferred transparently between the MS and the external data networks with a method known as encapsulation and tunneling: data packets are equipped with PS-specific protocol information and transferred between the MS and the GGSN.
  • QoS Quality of Service
  • 3G UMTS mobile networks QoS is a means for providing end users with satisfying service. QoS also enables efficient use of the spectrum resources. Because the invention will be described in terms of a UMTS QoS architecture, a brief overview of QoS in UMTS is provided. The 3G UMTS QoS architecture is described, including an explanation of the packet data protocol context (PDP context), a traffic flow template (TFT), and the QoS maintenance procedures for activated UMTS bearers. It is expected that the QoS characteristics associated with a radio communication are the most critical in the end-to-end chain. Within UMTS access networks, the radio network resources are managed on a per PDP context level, which corresponds to one or more user flow/data streams and a certain QoS level.
  • PDP context packet data protocol context
  • TFT traffic flow template
  • QoS maintenance procedures for activated UMTS bearers. It is expected that the QoS characteristics associated with a radio communication are the most critical in the end-to-end chain.
  • the QoS framework for 3G networks is specified in the 3G specification (3GPP) TS23.107.
  • the main focus is on the QoS architecture to be used in the UMTS level, where the list of QoS attributes applicable to UMTS Bearer Service and the Radio Access Bearer Service are specified along with appropriate mapping rules.
  • TS23.060 specifies the general mechanisms used by data packet connectivity services in the UMTS level, which includes the General Packet Radio Service (GPRS) in GSM and UMTS.
  • GPRS General Packet Radio Service
  • a network service is considered to be end-to-end, from a Terminal Equipment (TE) to another TE.
  • TE Terminal Equipment
  • a bearer service with clearly defined characteristics and functionality is set up from the source to the destination of a service.
  • the bearer service includes those aspects needed to enable the provision of a contracted QoS, e.g., control signaling, user plane transport, QoS management and functionality.
  • a UMTS bearer service layered architecture is depicted in Fig. 7.
  • Each bearer service on a specific layer offers its individual services using services provided by the layers below.
  • Bearers at one layer are broken down into underlying bearers, each one providing a QoS realized independently of the other bearers.
  • Service agreements are made between network components, which are arranged horizontally in Fig. 7.
  • the service agreements may be executed by one or more layers of service.
  • the UMTS bearer service consists of a Radio Access Bearer (RAB) service and a Core Network (CN) bearer service.
  • the RAB services is then divided into a radio bearer service and a Iu bearer service.
  • the Iu interface is the interface between the radio access network and the core network.
  • the terminal equipment (TE) may be a laptop and the mobile terminal (MT) may be a cellular radio handset.
  • the UTRAN may be made up of a combination of radio base stations called Node B's and radio network controllers (RNCs).
  • the Core Network (CN) Iu Edge Node may be a serving GPRS support node (SGSN), and the CN Gateway may be a gateway GPRS support node (GGSN).
  • SGSN serving GPRS support node
  • GGSN gateway GPRS support node
  • the QoS management functions in UMTS are used to establish, modify and maintain a UMTS Bearer Service with a specific QoS, as defined by specific QoS attributes.
  • the QoS management functions of all the UMTS entities ensure provision of the negotiated UMTS bearer service.
  • the UMTS architecture comprises four management functions in the control plane and four in the user plane.
  • the four control plane management functions are shown in Fig. 8:
  • Bearer Service Manager sets up, controls, and terminates the corresponding bearer service. Each BS manager also translates the attributes of its level to attributes of the underlying bearer service during service requests.
  • Translation function converts between external service signaling and internal service primitives including the translation of the service attributes, and is located in the MT and in the CN Gateway.
  • Admission/Capability control determines whether the network entity supports the specific requested service, and whether the required resources are available.
  • Subscription Control determines whether the user has the subscription for the bearer being requested.
  • the four user plane management functions are:
  • Classification function resides in the GGSN and in the MT. It assigns user data units (e.g. IP packets) received from the external bearer service from the remote terminal (or the local bearer service) from the local terminal to the appropriate UMTS bearer service according to the QoS requirements of each user data unit. This is where the traffic flow template (TFT) and packet filters are situated, as described below.
  • TFT traffic flow template
  • Mapping function marks each data unit with the specific QoS indication related to the bearer service to which it has been classified. For example, it adds different service code points to packets before putting them on the Iu or CN bearer.
  • Resource Manager distributes its resources between all bearer services that are requesting use of these resources.
  • the resource manager attempts to provide the QoS attributes required for each individual bearer service.
  • An example of resource manager is a packet scheduler.
  • Traffic conditioner is a shaping and policing function which provides conformance of the user data traffic with the QoS attributes of the concerned UMTS bearer service. This resides in the GGSN and in the MT as well as in the UTRAN.
  • the QoS management functions of the UMTS bearer service in the user plane are shown in Fig. 9. These functions together maintain the data transfer characteristics according to the commitments established by the UMTS bearer service control functions, expressed by the bearer service attributes.
  • the user plane uses the QoS attributes. The relevant attributes are provided to the user plane management functions by the QoS management control functions.
  • Fig. 10 Data transport may be optimized for the corresponding type of application data or for a bearer service of a certain class.
  • the main distinguishing factor between these classes is how delay sensitive the traffic is: Conversational class is meant for traffic which is very delay sensitive (for real-time services) while Background class is the most delay insensitive traffic class (for non-real time services). Bit error/packet loss rate is also a significant difference between the classes.
  • a set of bearer service attributes are standardized in UMTS as shown in the tables referenced below.
  • a certain QoS is requested by selecting a set of attribute values that describes the bearer requirement. Parameters differ depending on the type of bearer service requested.
  • Fig. 11 shows which attributes that are applicable to which traffic class.
  • Fig. 12 provides an overview of uses for different QoS attributes. The exact definitions of the QoS attributes can be found in TS23.107.
  • a subscription is associated with one or more Packet Data Protocol (PDP) addresses, i.e., IP addresses in the case of IP traffic.
  • PDP Packet Data Protocol
  • Each PDP address is described by one or more PDP contexts stored in the MS, the SGSN, and the GGSN. Default values are also available in the cellular system data base, e.g., the HLR, which holds the subscription information.
  • Each PDP context may be associated with a Traffic Flow Template (TFT). At most, one PDP context (associated with the same PDP address) may exist at any time with no TFT assigned to it.
  • TFT Traffic Flow Template
  • a PDP context is implemented as a dynamic table of data entries, comprising all needed information for transferring PDP PDUs between MS and GGSN, for example addressing information, flow control variables, QoS profile, charging information, etc.
  • the relation between UMTS bearer services and PDP context is a one-to-one mapping, i.e., if two UMTS bearer services are established for one PDP address, two PDP contexts are defined.
  • the PDP context procedures are standardized in TS23.060.
  • the concepts surrounding the QoS profile and the Traffic Flow Template (TFT) are relevant from the QoS perspective.
  • the UMTS QoS attributes have been selected and defined mainly for supporting efficient radio realization.
  • a QoS profile is defined by a set of UMTS QoS attributes.
  • the RNC obtains the pertinent radio access bearer (RAB) QoS profile from the SGSN during PDP context activation.
  • RRB radio access bearer
  • a Traffic Flow Template is a packet filter (or set of filters) that associates packets to the correct PDP context thereby ensuring that packets are forwarded with correct QoS characteristics.
  • the TFT enables the possibility of having several PDP contexts with varying QoS profiles, associated to a single PDP address.
  • the TFT is managed and initiated by the MT both for the uplink and downlink flows.
  • the uplink TFT resides in the MT, while the downlink TFT resides in the GGSN.
  • the downlink TFT is sent from the MT to the GGSN during PDP context activation / modification.
  • the downlink TFT's may be added to a PDP context that was created without one, and the contents may be modified as well.
  • Fig. 14 shows TFT packet filter attributes and valid combinations.
  • Each TFT has an identifier and an evaluation precedence index that is unique within all TFT's associated with the PDP contexts that share the same PDP address.
  • the MS manages the identifiers and the evaluation precedence indices of the TFT's, as well as the packet filter contents.
  • Some of the attributes in Fig. 14 may coexist in a packet filter while others mutually exclude each other. Only those attributes marked with an "X" may be specified for a single packet filter. All the marked attributes may be specified, but at least one has to be specified.
  • the PDP context signaling carries the requested and negotiated QoS profile between the nodes in the UMTS network. It has a central role for QoS handling in terms of admission control, negotiation, and modifying of bearers on a QoS level.
  • the PDP context signaling message exchanges are described below with reference to the numerals in Fig. 15.
  • An RRC connection establishment is performed. This procedure is needed for establishing a connection, but does not cover more from a QoS perspective than that the type of radio channel is roughly indicated.
  • the MS sends a PDP message, "Activate PDP context request," to the SGSN.
  • the requested QoS profile is included in this message.
  • the SGSN makes an admission check and might restrict the requested QoS if the system is overloaded.
  • the SGSN sends a RANAP message, "RAB Assignment
  • RANAP Radio Access Network Application Part
  • RAB radio access bearer
  • the RNC determines the radio- related parameters corresponding to the QoS profile, e.g., transport format set, transport format combination set, etc.
  • the UTRAN performs an admission control on this bearer.
  • the RNC sends an RRC message, "Radio Bearer Set-up," to the MS.
  • the RRC message includes the radio-related parameters that were determined in step 4.
  • the UTRAN and the MS apply the radio parameters and are ready to transfer traffic. To signal this, the MS sends a "Radio Bearer Set-up
  • the UTRAN sends a "RAB Assignment Complete" RANAP message to the SGSN.
  • a Trace procedure may be initiated. This is an operation and maintenance function for surveying subscribers.
  • the SGSN sends a "Create PDP Context Request" to the GGSN carrying the QoS profile.
  • the QoS profile may have different parameters than those requested by the MS in step 2.
  • an admission control is performed at the GGSN level, and the GGSN may restrict the QoS if, for example, the system is overloaded.
  • the GGSN stores the PDP context in its databases.
  • the GGSN returns the negotiated QoS to the SGSN in a "Create PDP Context Response" message and the SGSN stores the PDP context in its database.
  • the negotiated QoS is sent from the SGSN to the MS in an
  • admission control in UMTS is performed in a radio centric manner.
  • Fig. 16 shows the embodiment for control of an IP service using IP BS Managers in both possible locations in the UE and Gateway node. Fig. 16 also indicates the optional communication path between the IP BS Managers in the UE and the Gateway node.
  • the IP BS Managers use standard IP mechanisms to manage the IP bearer service. These mechanisms may be different from mechanisms used within the UMTS, and may have different parameters controlling the service.
  • the translation/mapping function provides the interworking between the mechanisms and parameters used within the UMTS bearer service and those used within the IP bearer service, and interacts with the IP BS Manager. If an IP BS Manager exists both in the UE and the Gateway node, it is possible that these IP BS Managers communicate directly with each other by using relevant signaling protocols.
  • IMS IP Multimedia Service
  • the IMS is based on IP application signaling, which in a preferred, example embodiment includes session initiation protocol (SIP) and session description protocol (SDP).
  • SIP is a signaling protocol to establish sessions
  • SDP is a text- based syntax to describe the session and includes, for example, the definition of each media stream in the session.
  • a policy system For multimedia sessions, it is important that network managers and services providers be able to monitor, control, and enforce the use of network resources and services based on "policies" derived from certain established criteria such as the identity/authority level of users and applications, traffic bandwidth requirements, security considerations, time of day/ week, etc. Because there are varying circumstances in which various entities are entitled to use the services they request, there is a need for rules, a need for enforcement methods of these rules, and a need for a "judge" to decide when they apply. Accordingly, three major components of a policy system include policy rules, which are typically stored in a policy database, policy enforcement, which may be implemented at Policy Enforcement Points (PEP), and Policy Decision Points.
  • PEP Policy Enforcement Points
  • COPS Common Open Policy Service
  • a policy may be regarded as a collection of rules that result in one or more actions when specific conditions exist.
  • Session level policy controls such as the service-based local policy control described in commonly-assigned U.S. Patent Application No. 09/861,817, entitled “Application Influenced Policy,” cannot automatically be applied to PDP contexts unless the relationship of the various media streams to the PDP context is known. That is because such relationships are under the control of the end user establishing the multimedia session, the various media streams, and the corresponding quality of service parameters associated with those media streams.
  • a chief problem addressed by this invention is how to communicate effectively and efficiently the relationship between a session, media flows in that session, and PDP context bearers established for those media flows in order to request, reserve, supply, and enforce the resources necessary to support each media flow at the PDP bearer level.
  • the interworking node To enable interworking between these two QoS domains with different signaling protocols, the interworking node must be able to receive service requests from one domain, and generate the necessary service request to the other domain. The interworking node must obtain the necessary service information for the service request to be generated. Where this information is not provided by the received service request, the interworking node must receive a "key" enabling it to access the additional required information from another source.
  • RSVP e.g., RSVP
  • PDP context information e.g., PDP context information
  • the present invention overcomes these and other problems by providing an efficient and effective mechanism for binding packet access/bearers in the UMTS to the multimedia streams in a session they support to permit session level control of those bearers, e.g., requesting, reserving, supplying, and enforcing IP level resources needed to support the session.
  • This mechanism also enhances the interaction between UMTS packet access bearers and quality of service reservation and management mechanisms employed by the IP backbone network.
  • IP-level elements in a PDP context activation/modification message include binding information to link each of plural media PDP contexts/data streams to a multimedia session and to a corresponding packet access bearer.
  • the present invention provides a method for use in setting up and orchestrating 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.
  • the mobile terminal uses the session packet access bearer, the mobile terminal initiates a multimedia session that includes a plurality of media data streams.
  • Media packet access bearers between the mobile terminal and the access point are established.
  • Media binding information is used to associate that multimedia session and each media data stream to one of the media packet access bearers used to transport a corresponding one of the media data streams between the mobile terminal and the access point.
  • a media data stream may be defined as the data flow generated by one single transcoding device or type, or by the aggregate of data flows generated by several transcoding devices or types.
  • the media binding information elements for several media data streams are all associated with the shared media packet access bearer.
  • the media binding information may be associated with quality of service information for the corresponding media data stream requested by the user application initiating the session.
  • quality of service and media binding information may be included in signaling used to set up the packet access bearers so that policies are applied to each packet access bearer to enforce the quality of service requested for each media data stream in the session.
  • the absence or presence of the media binding information in a packet access bearer setup message is useful in determining whether a packet access bearer is a general packet access bearer or a multimedia session packet access bearer.
  • basic packet data network IP connectivity services may be employed in the general case, (i.e., absence of media binding information).
  • enhanced packet data network-based services such as service- based local policy may be employed using the media binding information.
  • the media binding information may be used to authorize permissible quality of service for each of the packet access bearers and to obtain both session- related and media data stream-related rules to apply to each packet access bearer. Such rules may relate to admission and policy control for each of the media data streams in the session.
  • the session-related data may be used to identify one or more nodes and one or more networks involved in transporting one of the media data streams along a path between the access point through the packet data network to the remote user. If one of the media data stream-related demands on the packet access bearer is modified, the media binding information is also modified, and a new set of policy rules is obtained. Moreover, if the packet access bearer is modified on request by the UE, the current rules are checked to determine if the change is allowed, and if not, updated rules are obtained.
  • the present invention is adapted to a multimedia session in which a user employs a GPRS/UMTS network to access the packet data network, e.g., the Internet, to establish a multimedia session with a remote host.
  • a session signaling PDP context is established between the mobile terminal in a GPRS network using a corresponding session signaling GPRS bearer.
  • the GPRS network is coupled to a radio access network and to a multimedia system that provides multimedia session services.
  • a multimedia session is initiated between the mobile terminal and the remote host over the session signaling GPRS bearer in cooperation with a call service control server in the multimedia system.
  • Media binding information is created which associates each media data stream to the multimedia session.
  • the mobile terminal forwards the media binding information in a PDP context activation or modification message for each of the media data streams to bind each of the media PDP contexts/ GPRS bearers to a corresponding one of the media data streams in the multimedia session.
  • the GGSN in the GPRS network receives such PDP context messages and uses the media binding information to facilitate interworking to other packet networks connected to the GPRS network and to assist in reserving IP level quality of service resources for each media data stream from the GGSN to the remote host.
  • the quality of service resources for each media data stream from the GGSN to the remote host may be reserved using an Internet-based resource reservation protocol such as RSVP or differentiated services (DiffServ).
  • Quality of service resources for each media data stream in the multimedia session are reserved from the mobile terminal to the GGSN using PDP context messages.
  • the GGSN uses the media binding information to access a policy controller in the multimedia system and to obtain therefrom quality of service and IP policy enforcement information for each media data stream in the session.
  • the GGSN may function as an RSVP proxy for the mobile terminal using session related data to formulate RSVP bearer requests for each media data stream in the session.
  • the PDP context request message includes the media binding information as a PDP configuration option (PCO).
  • PCO PDP configuration option
  • the messages that include the PCO carrying the media binding information are well known GPRS messages for activation/creation of a secondary PDP context or for modification/update of a PDP context.
  • Fig. 1 is a block diagram of a high level IP network
  • Fig. 2 is a block diagram depicting an example of a network employing end-to-end integrated services
  • Fig. 3 is a block diagram depicting an example of a network employing an RSVP proxy
  • Fig. 4 is a block diagram depicting an example of a network employing end-to-end differentiated services
  • Fig. 5 is a block diagram depicting an example of a network employing
  • Fig. 6 is a block diagram depicting a mobile access data network modeled as a DiffServ network
  • Fig. 7 is a block diagram of a UMTS quality of service architecture
  • Fig. 8 is a block diagram depicting quality of service management for
  • Fig. 9 is a block diagram depicting quality of service management functions for UMTS bearer services in the user plane
  • Fig. 10 is a table of UMTS quality of services classes
  • Fig. 11 is a table of quality of service attributes
  • Fig. 12 is a table providing an overview of some uses for the quality of service attributes illustrated in Fig. 11;
  • Fig. 13 is a block diagram of the relationship between PDP address, PDP context, and TFT;
  • Fig. 14 is a table of valid combinations of TFT packet filter attributes
  • Fig. 15 is a diagram of PDP context message exchanges
  • Fig. 16 is a block diagram of the quality of service management functions for UMTS bearer services in the control plane and quality of service management functions for end-to-end IP quality of service;
  • Fig. 17 illustrates a communications system in which a multimedia session may be established between a mobile terminal and a remote host
  • Fig. 18 illustrates in flowchart form procedures for media binding in accordance with an example embodiment of the present invention
  • Fig. 19 illustrates in more detail a multimedia session in the communications system shown in Fig. 17;
  • Fig. 20 illustrates in block format various functions performed by the mobile terminal, packet data network access point, and multimedia system
  • Fig. 21 illustrates a GPRS/UMTS-based communication system for conducting multimedia sessions in accordance with another example embodiment of the present invention
  • Fig. 22 is a flowchart illustrating example procedures for establishing a multimedia session in the system shown in Fig. 21;
  • Fig. 23 is a signaling diagram illustrating various signals for establishing a multimedia session in accordance with one example, non-limiting embodiment of the present invention as applied to the system shown in Fig. 21.
  • a mobile terminal is used as one example of a user equipment (UE) allowing a user access to network services.
  • UE user equipment
  • the interface between the user equipment and the network is the radio interface.
  • the present invention is described using the term "mobile terminal,” the present invention may be applied to any type or configuration of user equipment that can communicate over a radio interface.
  • IP bearer service manager may be used to control the external IP bearer service through the external packet data network, e.g., the Internet, to the remote host.
  • the external packet data network e.g., the Internet
  • the remote host 20 can be a fixed or wireless device.
  • the mobile terminal 10 is coupled to a radio access network (RAN) 12 over the radio interface.
  • the RAN 12 is coupled to an Access Point in a packet-switched access network (PSAN) 14, which in turn is coupled to a Packet Data Network (PDN) 18 to which the remote host 20 is coupled.
  • PSAN packet-switched access network
  • PDN Packet Data Network
  • the basic traffic flow for a multimedia session (shown as solid lines) between the mobile terminal 10 and remote host 20 is transported via these three networks 12, 14, and 18.
  • the PSAN 14 and the PDN 18 communicate multimedia control signaling (shown as dashed lines) to a Multimedia System 16 that can be separate from or an integral part of the Packet Data Network 18.
  • the present invention provides an effective and efficient way to provide end-to-end IP quality of service and to manage that quality of service within each domain in the end-to-end path in a multimedia session using media binding information.
  • This media binding information permits interworking of resources owned or controlled by the UMTS network with resources in the external packet data network.
  • the media binding information provides a mechanism to support service-based policy enforcement on individual multimedia flows in the session.
  • a session packet access bearer (PAB) between the mobile terminal 10 and the access point 14 to the packet data network (PDN) 18 via the radio access network (RAN) 12 (block 32).
  • PDN packet data network
  • RAN radio access network
  • the mobile terminal uses the session packet access bearer to initiate the multimedia system a multimedia session with the remote host 20 that includes plural media data streams (block 34).
  • Media packet access bearers corresponding to each of the plural media data streams are established between the mobile terminal 10 and the access point 14 (block 35).
  • Media binding information is used to associate each media data stream in the session to one of the media access bearers used to transport each media data stream in the session (block 36).
  • the media binding information is used to retrieve session, media, and policy-related information from the multimedia system, which in turn is used to perform various control functions for the packet access bearer.
  • Example functions include admission control, packeting filtering and policing, and interworking at the access point (block 38).
  • Fig. 19 illustrates, in a functional block diagram format, elements involved in setting up a multimedia session.
  • the mobile terminal 10 includes Access Network Bearer Control 40 coupled to multimedia session control 42.
  • the Access Network Bearer Control block 40 transports internal bearer control signaling, which is not dedicated to a particular session, to an Access Network Bearer Control block 46 in the packet data network access point 14 transparently over the radio access network over a PDN signaling transport bearer.
  • Both Access Network Bearer Control blocks 40 and 46 assist in establishing a packet access bearer for setting up the session shown as the pipe entitled "transport of session signaling." Over this bearer, the mobile terminal 10 initiates a multimedia session including a plurality of media data streams with the remote terminal 20.
  • Each media data stream or "flow" is transported over a corresponding packet access bearer illustrated as a "transport of media flow” pipe coupled to a Forward Media Streams block 44 in the mobile terminal.
  • Two media flows 1 and 2 are shown for purposes of illustration in this multimedia session.
  • the multimedia system 16 in the packet data network 18 employs a Route Media Streams block 50 to route the packets in each media flow between the mobile terminal 10 and the remote terminal/host 20.
  • Multimedia system 16 also includes a Session Control and Policy Control block 48 that utilizes the session signaling from the Multimedia Session Control block 42 in the mobile terminal 10 to correlate each multimedia flow and its corresponding quality of service requirements with the session to establish necessary admission and policy enforcement rules for the session. Those rules are provided upon request to the Access Network Bearer Control block 46 which performs admission and policy enforcement operations for the session in accordance with the obtained session rules.
  • Fig. 20 is a block diagram that provides additional details of the control functions and signaling generally illustrated in Fig. 19. To simplify the illustration and discussion, the media flows are not shown in Fig. 20.
  • the mobile terminal determines media binding information specific to each media flow in the session (block 62).
  • the media binding information is included in packet access bearer setup signaling for each media flow packet access bearer established for the session between the mobile terminal 10 and the access point 14. See the bearer control signaling block in dashed lines containing the media binding information for each media flow. As illustrated in block 66 at the PDN access point, the media binding information for each flow is obtained from corresponding bearer setup messages. The media binding information is stored in the PDN access point as a part of the packet access bearer context characterizing the packet access bearer. In addition, the access point requests from the multimedia system rule(s) for each packet access bearer using the media binding information as an identifier. The multimedia system has stored the session identifier, session-related data, and media-related information for the requested session (block 68).
  • the multimedia system defines appropriate rules for each media flow and thus also for each packet access bearer in the session (block 70).
  • the multimedia system retrieves the rules using the media binding information as a "key" and provides them to the packet data network access point in a rule(s) response message.
  • the access point performs policy enforcement mechanisms such as one or more filters on each media data flow according to the received rules.
  • the interworking node must be able to receive service requests from one domain, and generate the necessary service request to the other domain.
  • the interworking entity in Fig. 16 is the IP BS manager, and it must obtain the service information needed for the service requests to be generated. Information that is not available in the received service request from one domain may be obtained from a Policy Decision Point coupled to the multimedia service, e.g., by using a key.
  • the Policy Decision Point is provided with session-specific and media-specific information from the multimedia system.
  • the IP BS manager receives an identifier for this information in the
  • the IP BS manager may request additional information needed from the Policy Decision Point in order to perform interworking and generate the service requests toward the external domain.
  • the present invention has particularly advantageous application to multimedia sessions involving a GPRS/UMTS network.
  • the present invention is not limited to this particular application or to the preferred example embodiment now described.
  • IMSS IP multimedia subsystem
  • the GPRS/UMTS-type network 80 is also coupled to an IP backbone network 84. This coupling (shown as a solid line) is used to transport user data IP packets.
  • the IMSS 82 is typically a part of (although it may be separate from and coupled to) an IP backbone network 84.
  • the remote host corresponding to user equipment (UE-B) 102 is coupled to the IP backbone network 84 through its home cellular network 86, and by signaling connection, to the IMSS 82.
  • UE-B user equipment
  • the mobile terminal 88 corresponding to UE-A 88 desires to establish a multimedia session with UE-B 102.
  • the packet traffic for this session follows the solid line couplings between the various nodes.
  • the session is established and managed using Session Initiation Protocol (SIP), and therefore, the user equipments 88 and 102 correspond to SIP User Agents (SIP UA).
  • UE-A 88 is coupled via the Radio Access Network (RAN) 90 to the GPRS packet access network 92.
  • the GPRS network 92 includes one or more SGSNs 94 coupled to one or more GGSNs 96.
  • the IP multimedia system 82 includes a Call State Control Function, in this example a proxy-CSCF (P-CSCF) 98 is shown, and a Policy Control Function (PCF) 100.
  • P-CSCF 98 and PCF 100 may be implemented on the same or different servers.
  • the Proxy-Call State Control Function 98 functions as a SIP proxy for the SIP user agent UE-A 88.
  • a session signaling GPRS bearer is established between UE-A and the GPRS network 92 using well-established GPRS PDP context activation messages.
  • This session signaling GPRS bearer corresponds to a first PDP context signaling (block 112).
  • UE-A requests a multimedia session with the SIP UA remote UE-B over the session signaling GPRS bearer via the RAN 90, the GPRS network 92, the IP multimedia subsystem 82, the IP backbone network 84, and UE-B's home cellular network 86 (block 114).
  • This request may be in the form of an SIP/SDP message which contains sufficient information about the session, such as the source (UE-A) and destination (UE-B) end points, bandwidth requirements, and the characteristics of the media exchange, etc. to trigger an authorization of QoS resources procedure in the Proxy-Call State Control Function 98.
  • the Policy Control Function 100 authorizes, if appropriate, the required quality of service resources for the session and installs an IP bearer level policy for the session and each media flow based on the information from the Proxy- Call State Control Function 98.
  • the Policy Control Function 100 generates an authorization "token" for the session (session identifier) and sends it to UE-A and UE-B (block 115).
  • the multimedia session is authorized, and the policy control function 100 stores session information for each of the media flows in the session.
  • the mobile terminal generates media binding information (MBI) for each media data stream in the session (block 116).
  • the mobile terminal requests a PDP context for each media stream and also provides the MBI to the GGSN in the PDP context request message.
  • the MBI is used to retrieve session, media, and policy related information from the multimedia system (block 118).
  • One MBI may be included per PDP context, or multiple MBIs may be included per PDP context.
  • the MBI may also be used in a PDP context modification message. Because a first PDP context activation message was initially generated to set up the session control signaling GPRS bearer from the mobile terminal UE-A to the GGSN, the PDP context request in block 118 is called a "secondary" PDP context request.
  • the session, media, and policy related information is used to decide if the PDP context is allowed to be established (admission control).
  • the admission control also considers if the mobile terminal is allowed to use network resources from the GGSN to the remote SIP UA
  • the media binding information associates the PDP context bearer with the policy information for that media stream.
  • the PDP configuration options parameter present in the existing GPRS PDP context activation/modification message format may be used to carry the media binding information for each PDP context corresponding to one of the media flows.
  • the media binding information includes sufficient information to identify its corresponding media flow and GPRS bearer as well as the session.
  • the media binding information is used by the UE-A, GGSN 96, and the PCF 100 to uniquely identify, monitor, and control the IP media flows and bearers from the session level.
  • the media binding information (MBI) for each of the media data streams is included in the corresponding secondary PDP context request using well- established GPRS-PDP context messaging signals. Again, it is possible to include one MBI per PDP context, or multiple MBIs per PDP context.
  • the GGSN uses the MBIs to pull policy decisions from the PCF. More specifically, the session, media, and policy related information is stored together with the MBI, PDP context identifier, and other PDP context attributes in the GGSN. Based on that stored information and the policy decisions pulled from the PCF, the GGSN performs filtering, policy control, and RSVP/DS interworking (block 122).
  • FIG. 23 An example signaling flow diagram for an example multimedia session between UE-A and UE-B is shown in Fig. 23 and now described.
  • the UE establishes a first PDP context with the GGSN to establish a GPRS bearer for session signaling needed to establish the multimedia session.
  • the UE-A registers with the proxy-CSCF before sending a SIP INVITE message on the GPRS signaling bearer to the CSCF to setup the IP multimedia session.
  • the INVITE message includes the session details regarding the number of media flows and requested corresponding quality of service.
  • the CSCF authenticates the UE-A as a subscriber and authorizes the session.
  • the SIP INVITE message is forwarded to UE-B via external networks.
  • the UE-B confirms the session request in a SIP "183" message returned to the CSCF.
  • the SIP 183 is an acknowledgement message to the SIP INVITE message.
  • the CSCF requests from the PCF a session identifier (ID) for the session and communicates session-related and media-related data to the PCF.
  • the session ID corresponds to the authentication token in block 116 in Fig. 22.
  • the PCF registers the session-related data and the media-related data, makes policy decisions for the session, issues the session ID (authorization token), and returns it to the CSCF.
  • the CSCF confirms the session, and delivers the session ID in a SIP 183 message to the UE-A.
  • the UE-A determines media information from each media stream, and generates media binding information (MBI) for each media stream using the session ID and the media information.
  • the UE-A may receive the MBI from the CSCF in the SIP 183 message or from another entity. Still further, the UE-A may create the MBI using some other procedure that does not employ the session ID.
  • the UE-A activates a second PDP context (i.e., by sending a secondary PDP context request message to the SGSN) for each media stream.
  • the PDP configuration options (PCO) parameter is an attribute that is part of the well-known GPRS messages for control of GPRS bearers (PDP contexts).
  • a PCO in each secondary PDP context request message preferably includes the media binding information (MBI) for each media stream.
  • the GGSN uses the MBI as an identifier for each media stream and requests the policy/rules for the session and media stream in a COPS REQ message.
  • the PCF retrieves the session information and policy decisions associated with the MBI for each media stream and returns the policy rules and other session-related and media-related information to the GGSN in a COPS DEC message.
  • the GGSN enforces the policy and acknowledges the request for each secondary PDP context.
  • the GGSN responds with a COPS RPT message.
  • Policy control allows the network operator to control the authorization and usage of GPRS bearers based on the session attributes. For example, the network operator may apply policies such as:
  • GPRS bearer a high bandwidth real time GPRS bearer
  • media stream with relevant characteristics e.g., a high quality video conference
  • the GGSN may also use the session-related and media-related information, (e.g., the UE-B address), to enable itself as an RSVP proxy for the UE-A, generating and terminating RSVP signaling for each media stream to/from UE-B.
  • the GGSN As an RSVP proxy, the GGSN generates an RSVP PATH message for each media data stream to UE-B, which is then confirmed by an RSVP RESV message from the UE-B. This is done for the establishment of the RSVP flow from the GGSN to the UE-B.
  • the GGSN RSVP proxy responds to each RSVP PATH message from UE-B with a RSVP RESV message. This is done for the establishment of the RSVP flow from the UE-B to the GGSN.
  • the two RSVP Flows are established for each bidirectional media data stream for which GGSN has established the RSVP proxy function. Furthermore, the GGSN may use the obtained rules and session/media-related information to perform admission control. For example, the address of UE-B may be used to identify which external network and nodes the media stream shall pass through, and to determine if admission is allowed to these nodes/networks .
  • RSVP is shown in this signaling diagram, other external network resource reservation protocols may be used, e.g., DiffServ.
  • the GGSN uses the obtained rules and session/media-related information to reserve and establish a corresponding transport path with the requested QoS through the external packet data network to the UE-B.
  • the necessary interworking between the GPRS/UMTS bearer and the IP transport through the external packet data network for a certain media stream is supported by contexts stored in the GGSN containing the MBI, and for example, the obtained rules and session/media-related information, attributes and status information for the GPRS bearer, and attributes and status information associated with RSVP.
  • the media binding information may be used to enhance interworking options/functionality at the GGSN, for example, to obtain the necessary parameters for RSVP signaling, which it does not receive in the PDP context signaling, and thus provide interworking to the RSVP enabled domains.
  • enhanced interworking using the MBI include performing more complex admission control decisions by obtaining, for example, the destination IP address, providing access to resources reserved for traffic accessing a specific IP multimedia service by obtaining multimedia session-related event triggers, using the obtained destination address to select an external packet data network quality of service mechanism or interface, and applying additional traffic controls for the bearer, (e.g., restrictive source/destination address and port numbers), defined based on the multimedia application that is using the bearer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Quality & Reliability (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Security & Cryptography (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Afin d'établir une session multimédia impliquant un terminal mobile, un support d'accès par paquets à une session est installé entre le terminal mobile et un point d'accès à un réseau de données par paquets, par le biais d'un réseau d'accès radio. Ce point d'accès est relié à un système multimédia fournissant des services de session multimédia. A l'aide du support d'accès par paquets à une session, une session multimédia impliquant ledit terminal mobile est initiée, laquelle session comprend une pluralité de flux de données média. Des supports d'accès par paquets au média sont installés entre le terminal mobile et le point d'accès. Des informations de liaison média sont utilisées pour associer ladite session multimédia et chaque flux de données média à un des supports d'accès par paquets au média, utilisé pour transférer un flux de données média correspondant entre le terminal mobile et le point d'accès. Ces informations de liaison média peuvent être utilisées de diverses manières pour établir et gérer la session multimédia ainsi que les supports d'accès par paquets au média.
EP01981280A 2000-11-06 2001-11-06 Procede et appareil pour coordonner des exigences de qualite de service pour des flux de donnees media dans une session multimedia avec des ressources de support ip Withdrawn EP1332632A2 (fr)

Applications Claiming Priority (11)

Application Number Priority Date Filing Date Title
US24650100P 2000-11-06 2000-11-06
US246501P 2000-11-06
US24811000P 2000-11-13 2000-11-13
US248110P 2000-11-13
US26076501P 2001-01-10 2001-01-10
US260765P 2001-01-10
US26773701P 2001-02-09 2001-02-09
US267737P 2001-02-09
US985631 2001-11-05
US09/985,631 US20020062379A1 (en) 2000-11-06 2001-11-05 Method and apparatus for coordinating quality of service requirements for media flows in a multimedia session with IP bearer services
PCT/SE2001/002450 WO2002037869A2 (fr) 2000-11-06 2001-11-06 Procede et appareil pour coordonner des exigences de qualite de service pour des flux de donnees media dans une session multimedia avec des ressources de support ip

Publications (1)

Publication Number Publication Date
EP1332632A2 true EP1332632A2 (fr) 2003-08-06

Family

ID=27540242

Family Applications (1)

Application Number Title Priority Date Filing Date
EP01981280A Withdrawn EP1332632A2 (fr) 2000-11-06 2001-11-06 Procede et appareil pour coordonner des exigences de qualite de service pour des flux de donnees media dans une session multimedia avec des ressources de support ip

Country Status (3)

Country Link
EP (1) EP1332632A2 (fr)
AU (1) AU2002212935A1 (fr)
WO (1) WO2002037869A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11729588B1 (en) 2021-09-30 2023-08-15 T-Mobile Usa, Inc. Stateless charging and message handling

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7483989B2 (en) * 2001-03-13 2009-01-27 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for establishing a protocol proxy for a mobile host terminal in a multimedia session
US7551888B2 (en) 2002-04-22 2009-06-23 Nokia Corporation Method and system of displaying content associated with broadcast program
BR0309410A (pt) * 2002-04-22 2005-02-01 Nokia Corp Método, sistema de mìdia e terminal do usuário para coletar a informação sobre a audiência de um fluxo de mìdia de radiodifusão
US6788676B2 (en) 2002-10-30 2004-09-07 Nokia Corporation User equipment device enabled for SIP signalling to provide multimedia services with QoS
US6888821B2 (en) * 2003-02-10 2005-05-03 Nokia Corporation Dynamic media authorization in mobile networks
US7826353B2 (en) * 2003-05-05 2010-11-02 Nokia Corporation Method, system and network element for authorizing a data transmission
EP1868335A1 (fr) * 2006-06-12 2007-12-19 Thomson Licensing S.A. Procédé de transmission de données entre une station émettrice dans un premier réseau et une station réceptrice dans un deuxième réseau, et dispositif pour commande de la communication entre la station émettrice dans le premier réseau et la station réceptrice dans le deuxième réseau
EP1868329A1 (fr) * 2006-06-12 2007-12-19 Deutsche Thomson-Brandt Gmbh Procédé de transmission de données entre une station émettrice dans un premier réseau et une station réceptrice dans un deuxième réseau, et dispositif pour commande de la communication entre la station émettrice dans le premier réseau et la station réceptrice dans le deuxième réseau
EP2600589A1 (fr) * 2011-11-30 2013-06-05 British Telecommunications public limited company Découverte des services d'infrastructure de réseau de données

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1096743A1 (fr) * 1999-10-25 2001-05-02 Lucent Technologies Inc. Réseau de communication par radio
US20010027490A1 (en) * 2000-01-25 2001-10-04 Gabor Fodor RSVP handling in 3G networks
CN1201534C (zh) * 2000-05-22 2005-05-11 艾利森电话股份有限公司 应用影响策略

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO0237869A2 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11729588B1 (en) 2021-09-30 2023-08-15 T-Mobile Usa, Inc. Stateless charging and message handling

Also Published As

Publication number Publication date
AU2002212935A1 (en) 2002-05-15
WO2002037869A2 (fr) 2002-05-10
WO2002037869A3 (fr) 2002-08-15

Similar Documents

Publication Publication Date Title
US7546376B2 (en) Media binding to coordinate quality of service requirements for media flows in a multimedia session with IP bearer resources
US20020062379A1 (en) Method and apparatus for coordinating quality of service requirements for media flows in a multimedia session with IP bearer services
US20030120135A1 (en) Method for remote medical consultation and care
US7106718B2 (en) Signaling quality of service class for use in multimedia communicatations
US7483989B2 (en) Method and apparatus for establishing a protocol proxy for a mobile host terminal in a multimedia session
EP1332627B1 (fr) Procede et appareil permettant de coordonner la taxation de services fournis dans une session multimedia
US20060168303A1 (en) Method and apparatus for coordinating charging for services provided in a multimedia session
US20030172160A9 (en) Method and apparatus for coordinating end-to-end quality of service requirements for media flows in a multimedia session
KR101098715B1 (ko) 데이터 전송 시에 패킷 필터를 설치하는 방법 및 장치
JP4536990B2 (ja) アプリケーション影響ポリシー
WO2001056250A1 (fr) Manipulation rsvp en reseaux 3g
JP2007151187A (ja) Ｐｄｐコンテクストエラー取り扱い方法
EP1820305B1 (fr) Procede et systeme permettant la mise en oeuvre d'une gestion de regles locales sblp dans un systeme integre wlan-gsm/3g
WO2002037753A2 (fr) Liaison de medias afin de coordonner les exigences en matiere de qualite de service pour des flux de medias dans une session multimedia avec des ressources de support ip
EP1332632A2 (fr) Procede et appareil pour coordonner des exigences de qualite de service pour des flux de donnees media dans une session multimedia avec des ressources de support ip
WO2002058325A2 (fr) Procede et systeme de coordination de criteres de qualite de service de bout en bout pour des trains de donnees de media dans une session multimedia
KR100879164B1 (ko) 통신 네트워크에서 서비스 품질 관리를 위한 결합 메커니즘

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20030410

AK Designated contracting states

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

AX Request for extension of the european patent

Extension state: AL LT LV MK RO SI

RIN1 Information on inventor provided before grant (corrected)

Inventor name: WILLIAMS, BRIAN, CHARLS

Inventor name: WIDEGREN, INA, BIRGITTA

Inventor name: TAN, THIAN, JOO

Inventor name: OYAMA, JOHNSON

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

17Q First examination report despatched

Effective date: 20071214

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20160601