EP1655923A2 - Système et procédé pour la provision de qualité de service dans une bouble locale - Google Patents

Système et procédé pour la provision de qualité de service dans une bouble locale Download PDF

Info

Publication number
EP1655923A2
EP1655923A2 EP05110241A EP05110241A EP1655923A2 EP 1655923 A2 EP1655923 A2 EP 1655923A2 EP 05110241 A EP05110241 A EP 05110241A EP 05110241 A EP05110241 A EP 05110241A EP 1655923 A2 EP1655923 A2 EP 1655923A2
Authority
EP
European Patent Office
Prior art keywords
service
network
level
client
provider
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
EP05110241A
Other languages
German (de)
English (en)
Other versions
EP1655923A3 (fr
Inventor
David Jason Krantz
Douglas M. Nortz
Robert Sayko
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.)
AT&T Corp
Original Assignee
AT&T Corp
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
Application filed by AT&T Corp filed Critical AT&T Corp
Publication of EP1655923A2 publication Critical patent/EP1655923A2/fr
Publication of EP1655923A3 publication Critical patent/EP1655923A3/fr
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2801—Broadband local area 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
    • 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
    • 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/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
    • 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
    • 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
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • 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/74—Rating aspects, e.g. rating parameters or tariff determination apects
    • H04M2215/7414—QoS

Definitions

  • Telecommunications networks such as hybrid fiber coax (“HFC”) networks
  • HFC hybrid fiber coax
  • service problems include dropped packets, latency, lost packets, and corrupted packets.
  • QoS Quality of Service
  • the cables are generally owned and operated by a multiple system operator (“MSO”).
  • MSO multiple system operator
  • VoIP Voice over Internet Protocol
  • a subscriber to a telecommunications service such as a Voice over Internet Protocol (“VoIP”) service, receives the service through what is known in telecommunications terms as the "last mile” or "local loop" of the HFC network. Because the local loop is operated by the MSO, a provider of the service cannot provide QoS to the subscriber. Accordingly, there is a need for providing QoS over the local loop.
  • VoIP Voice over Internet Protocol
  • the level of service is communicated to the second network provider and, subsequent to receiving the service request, the level of service is purchased from the second network provider to guarantee the client the level of service when accessing the second network.
  • a system having a first element in a first network operated by a first network provider, receiving a service request from a client for a service application provided by the first service provider, a second element in the first network analyzing the service request and determining a level of service that is to be provided to the service application and a third element in the first network communicating the level of service to a second network provider and completing a transaction for the purchase of the level of service in a second network operated by the second network provider, wherein the client accesses the service application provided by the first network provider via the second network using the purchased level of service on the second network.
  • a method including receiving in a first network operated by a first network provider, a service request from a second network provider for a level of service in the first network, allocating the level of service within the first network when it is determined that the service request is valid, initiating a transaction to charge the second network provider for the level of service in the first network, receiving a reservation request from a client to use the allocated level of service within the first network and enabling a media path for the client within the first network, wherein the media path includes the level of service.
  • a system having a policy server in a first network operated by a first network provider, a service request from a second network provider for a level of service in the first network, the policy server allocating the level of service within the first network when it is determined that the service request is valid and initiating a transaction to charge the second network provider for the level of service in the first network and a termination system receiving the level of service allocation from the policy server and further receiving a reservation request from a client to use the allocated level of service within the first network, the termination system enabling a media path for the client within the first network, wherein the media path includes the level of service.
  • Fig. 1 shows an exemplary embodiment of a VoIP architecture.
  • Fig. 2 shows an exemplary embodiment of a system for providing QoS according to the present invention.
  • Fig. 3 shows an exemplary embodiment of a method for providing QoS according to the present invention.
  • the present invention may be further understood with reference to the following description and the appended drawings, wherein like elements are referred to with the same reference numerals.
  • the exemplary embodiment of the present invention describes a method for providing Quality of Service ("QoS") in a telecommunications network. More specifically, the exemplary embodiment describes a method of providing QoS in a hybrid fiber coax ("HFC") network that delivers Voice over Internet Protocol (“VoIP”) services.
  • QoS Quality of Service
  • HFC hybrid fiber coax
  • VoIP Voice over Internet Protocol
  • the present invention is not limited to VoIP services.
  • the exemplary embodiments are described with reference to VoIP services because currently this an example of a type of service where QoS is an important factor because customers may hear the effects of dropped or delayed packets.
  • any service which desires or requires a higher level of service than the normal packet transmission service may implement the present invention.
  • the provider of these services may not be the provider of the "last mile" or "local loop" to the end customer.
  • the service provider e.g., VoIP service provider
  • VoIP service provider is relying on the owner of the HFC infrastructure to provide QoS for the VoIP packets. Because the VoIP service provider does not control this last mile, the VoIP service provider cannot make direct QoS guarantees to the end customer. This places these VoIP service providers at a competitive disadvantage because they cannot make this guarantee.
  • the present invention provides a system and method for the service provider to have reliable and guaranteed access to the last mile. It also allows the HFC infrastructure owner to generate revenue that may have otherwise gone to a third party such as a local exchange carrier ("LEC").
  • LEC local exchange carrier
  • the exemplary embodiments of the present invention provide for a mutually beneficial relationship to be arranged between the service provider and the owner/operator of the HFC network.
  • Fig. 1 shows an exemplary VoIP architecture 100 for a VoIP service that may utilize the exemplary embodiments of the present invention to guarantee QoS to its customers.
  • the VoIP architecture 100 is divided into several layers. Each layer comprises a distinct function or group of related functions.
  • the VoIP architecture 100 may include a Resource Layer 110, an Operations Support Layer 120, an Access Layer 130, a Core Network Layer 140, a Connectivity Layer 150, and an Applications Layer 160.
  • the Resource Layer 110 provides network resources used to provide a VoIP service such as AT&T Corp.'s CallVantage® service.
  • the network resources may include systems which are owned and operated by a VoIP provider and/or a third party.
  • the Operations Support Layer 120 includes components for managing a VoIP network. These components may include applications, databases, and a data communications network.
  • the Access Layer 130 provides for communication between a subscriber of the VoIP services and the Connectivity layer. Devices which may be part of the Access Layer 130 include the hardware with which a subscriber to a VoIP service might access the service. For example, the hardware may include a telephone, a cable modem, a computing device, etc.
  • the Access Layer 130 may also include communications networks, such as a multiple system operator ("MSO") IP network and a Signaling System 7 (“SS7”) network.
  • MSO multiple system operator
  • SS7 Signaling System 7
  • the Access Layer 130 may also include a cable modem termination system (“CMTS”) and other devices that form an MSO's core network (e.g., policy servers, record keeping servers, etc.).
  • the Core Network Layer 140 provides a network for the routing and transport of IP packets, and overlaps with the Connectivity Layer 150.
  • the Core Network Layer 40 may include call control elements, media servers, and a Session Initiation Protocol ("SIP") border element ("BE") which translates access protocols to and from SIP as well as provides signaling, media control, security, and call admission control (“CAC”) functions.
  • SIP Session Initiation Protocol
  • BE border element
  • CAC call admission control
  • the Connectivity Layer 150 provides capabilities for creating, joining, removing, and reporting the status of call legs. Included in the Connectivity Layer 150 are the SIP BE, a Communications Assistance for Law Enforcement Act of 1994 ("CALEA") server, a CAC unit, a call control element ("CCE"), an Enhanced 911 (“E911”) server, and a media server.
  • the Applications Layer 160 includes one or more application servers which provide services. The application server(s) may direct the CCE to create, join, remove, and modify the call legs. The application server(s) may also create a call leg to the media server to access services provided by the media server. As described above, this reference to a VoIP service is only exemplary and some of the components described above, will be described in greater detail below in describing the exemplary embodiments of the present invention.
  • Fig. 2 shows an exemplary embodiment of a system 1 for providing QoS for a service from a service provider that does not own the last mile, e.g., the HFC network.
  • the system 1 will be described with reference to an exemplary method 400, shown in Fig. 3, that may be implemented on the system 1 for the purpose of providing a QoS guarantee to a service of the service provider.
  • the system 1 may be divided into an MSO core network 200 and a provider core network 300.
  • the system 1 utilizes the PacketCableTM Multimedia Architecture which is a project led by Cable Television Laboratories, Inc. ("CableLabs®") with the goal of defining interface specifications for interoperable equipment providing IP-based services (e.g., VoIP) over HFC systems.
  • PacketCableTM Multimedia Architecture which is a project led by Cable Television Laboratories, Inc.
  • IP-based services e.g., VoIP
  • the system 1 is compatible with the VoIP architecture 100 and includes many of the components discussed above with reference to the VoIP architecture 100. Those skilled in the art will understand that the omission of certain of the above-discussed components does not imply that these components are neither essential nor desirable to the operations of the system 1. In addition, one skilled in the art would understand that the system 1 may be easily adapted for compatibility with other VoIP service architectures and architectures for different types of non-VoIP services.
  • the MSO core network 200 may include an embedded multimedia terminal adapter ("EMTA") 210 which includes a client communication device 212 and a cable modem 214.
  • the client 212 may be any type of device that has communication capability, for example, an IP-enabled phone utilizing an Ethernet connection, a computing device with communication capability, etc.
  • the cable modem 214 is the component that connects the client 212 to the MSO core network via, for example, a HFC cable.
  • the EMTA 210 and its components 212, 214 are shown as autonomous components that are neither part of the MSO core network 200 nor the provider core network 300.
  • these components may be considered to be autonomous because they are resident at the customer's premises or as part of the either the MSO core network 200 or the provider core network 300.
  • the service provider since the service provider is providing the application that will be requesting the QoS guarantee, it may be considered that the EMTA 210 and its components 212, 214 are under the control of the service provider.
  • the client 212 requests QoS for a particular service (e.g., VoIP service).
  • this request is shown as being transmitted from the client 212 to a Class 5 application 340 residing on the provider core network 300.
  • the request is shown as being transmitted directly from the client 212 to the Class 5 application 340 using SIP as implemented in the provider network 300.
  • Fig. 2 only shows the request in a functional manner and that there may be many components that are present for communications to be completed from the client 212 to the Class 5 application 340.
  • the client 212 may not use the SIP protocol and thus, there may be an intermediate component that translates the message from the client 212 into a SIP message.
  • the QoS service request will include the standard items which are normally included in SIP messages, e.g., number (IP address) to be called, number (IP address) of caller, etc.
  • the Class 5 application 340 will receive the QoS request and pass the request to the Call Admission Control ("CAC") unit 350.
  • a QoS application manager is included in the CAC unit 350 for the purpose of analyzing the QoS request and determining the QoS requirements for the intended service application.
  • a standard SIP message for a VoIP call will include sufficient information for the QoS application manager to determine the QoS requirements in the same manner as if the call were being completed using the provider core network 300 without the use of the MSO network, i.e., the level of QoS that the service provider desires to apply to the call.
  • the class 5 application 340, the CAC unit 350 and/or another component of the provider network 300 in communication with the CAC unit 350 may also provide information that the QoS application manager may use to determine the QoS requirements for the application, e.g., a level of service guaranteed to the client 212, etc.
  • QoS requests that are transmitted in other protocols may need to include specific information that allows the QoS application manager to make a determination as to the QoS requirements of the requested service application.
  • the class 5 application 340 is also connected to the service provider's billing server 310 for the purposes of collecting billing information for the call.
  • This billing information may be information that is used to bill the client 212, e.g., a caller's number, a callee's number, a duration of a call, etc.) as well as network monitoring information (e.g., a total number of packets sent/received, an average packet size, an average transmission time, etc.).
  • the billing server 310 may also be used to verify the charges that are due to the MSO from the service provider for the purchase of the QoS guarantee for the particular call.
  • the QoS request may ultimately result in the wholesale purchase of a QoS guarantee by the service provider from the MSO.
  • the service provider may keep independent records of these purchases to verify any charges that are received from the MSO.
  • the service provider sends the QoS requirements to the MSO in order to make a wholesale purchase of the QoS guarantee for the particular service application.
  • the QoS requirements are initially sent within the provider core network from the CAC unit 350 to a Common Open Service Policy protocol - Session Initiated Protocol border element ("COPS-SIP BE") 336.
  • COPS-SIP BE 336 will receive the QoS requirements in the SIP protocol from the CAC unit 350 and convert the QoS requirements into the COPS protocol for the purpose of transmitting the QoS requirements to the MSO core network 200.
  • the QoS requirements will be received by a policy server 224 in the MSO core network 200.
  • the policy server 224 will determine whether the QoS requirements are valid.
  • the policy server 224 may include a set of rules that are used to validate incoming requests for QoS requirements.
  • the set of rules may include any type of rules that the MSO may desire to evaluate the QoS requests.
  • the message that is sent from the COPS-SIP BE 336 may include an indication of the service provider that is making the request for the QoS purchase.
  • a rule may include a check of whether the MSO has a contract or agreement with the identified service provider (or whether the message includes a service provider identification).
  • the message may also include the IP address or other identifier of the client 212.
  • the policy server 224 may include a rule that checks that the client 212 has access to the MSO's HFC network.
  • the rules may also be network based rules such as comparing the current capacity of the MSO's network to determine if there is network capacity to make the purchase of a QoS guarantee possible.
  • network based rules such as comparing the current capacity of the MSO's network to determine if there is network capacity to make the purchase of a QoS guarantee possible.
  • capacity based rules may not be applicable, i.e., the MSO may not have an option of denying the request unless there is some other reason.
  • this example was provided to show that the policy server 224 may implement any type of rule to evaluate the incoming request.
  • the policy server 224 determines that the QoS requirements are not valid in step 420, in step 425, the policy server 224 will send a message back to the service provider via the COPS-SIP BE 336. The message will then be relayed to the CAC unit 350 and may be sent via the Class 5 application 340 to the client 212. The message may indicate the reasons for the denial of QoS so that the QoS application manager of the CAC unit 350 can cure the defect or indicate to the client 212 the defect. If the QoS request is denied, the process ends and the client 212 does not receive the QoS guarantee for the service application.
  • the process continues to step 430 where the policy server 224 sends a policy set message to a CMTS 222 in the MSO core network 200.
  • the CMTS 222 may be included as part of a resource control arrangement 220 which also includes the policy server 224.
  • the policy set message may include information that the CMTS 222 may use to set up a media path for the client 212.
  • the policy set message may provide the parameters that should be guaranteed for a media path that is enabled for the client 212, e.g., maximum latency, maximum number of dropped packets, etc.
  • the policy server 224 may also include rules relating to the QoS guarantee that should be delivered to a particular client or class of clients based on the service provider.
  • a service provider may have a standing agreement with the MSO that any request from the service provider should have a predetermined level of service.
  • the rules contained therein may indicate the predetermined level of service and this information may be forwarded to the CMTS 22 in the policy set message.
  • the MSO core network 200 has been authorized to provide the client 212 with a defined QoS to meet the QoS requirements identified in the QoS request from the client 212 to the service provider. Described in another manner, the MSO has provided the service provider with a QoS guarantee that it will meet the QoS requirements defined in the message sent to the policy server 224. Thus, the service provider may guarantee the client 212 is provided with a desired level of service, for example, as defined in a Service Level Agreement ("SLA").
  • SLA Service Level Agreement
  • the service provider does not need to pre-purchase the QoS guarantee from the MSO, but may purchase the QoS guarantee on-demand as client 212 (or other clients) need access to the MSO's core network 200.
  • the service provider and the MSO may have a standing agreement as to the cost to the service provider for particular QoS guarantees, but the exemplary embodiments of the present invention alleviates the need to actually purchase the QoS guarantees until they are needed.
  • the client 212 may interact with the CMTS 222 to reserve the QoS guarantee for the service application.
  • the client 212 may communicate with the MSO core network 200 via the cable modem 214 as shown in Fig. 2. Since the exemplary MSO core network 200 includes a last mile HFC arrangement, the cable modem 214 is used to provide an interface between the client 212 and the CMTS 222 of the MSO core network 200.
  • the client 212 may communicate the QoS reservation, for example, in accordance with the Data Over Cable Service Interface Specification ("DOCSIS”) DSx developed by CableLabs®, RSVP+ messaging, etc.
  • DOCSIS Data Over Cable Service Interface Specification
  • the reservation sent by the client 212 may add, change or delete QoS within the authorized envelope with the CMTS 222.
  • the policy server 224 may provide the CMTS 222 with a specific QoS envelope in the policy set message based on the QoS requirements sent by the service provider.
  • the client 212 may desire a different QoS than the one that has been set aside for the service application.
  • the CMTS 222 may allow the client 212 to modify the original request.
  • the client 212 commits to the QoS reservation, i.e., the client sends a message to the CMTS 222 indicating that the client 212 will use the reserved QoS for the service application, e.g., a VoIP phone call.
  • the exemplary embodiment of the present invention uses a two-stage reservation and commit model for the client 212.
  • the present invention is not limited to a two-stage reservation and commit model, e.g., a one stage commit to the QoS is also possible.
  • the CMTS 222 enables a media path for the client 212 into the MSO IP network 240.
  • the client 212 via the cable modem 214 has access via the last mile HFC network of the MSO to the MSO IP network 240 and, as described above, the client 212 has a QoS guarantee for the media path that is enabled.
  • the client 212 may, for example, place a VoIP call that is routed via the MSO IP network 240 to the provider IP network 330 via a media path border element 338.
  • the provider network 330 may then route the VoIP call as appropriate, e.g., to the PSTN 320 via the network gateway border element (NGBE) 332, to another IP phone on the service provider or other provider's network, etc.
  • NGBE network gateway border element
  • other services may be provided for the call using the application server 334, e.g., call-related services, such as caller ID, call waiting, and conference calling.
  • the exemplary embodiments of the present invention are not concerned with the treatment of the service application (e.g., a VoIP call) once it reaches the provider IP network 330, but rather the guaranteeing of QoS for the service application on the MSO HFC network.
  • the service provider is able to guarantee the client 212 that they will have a desired level of service for the service application, even though the service provider does not own, operate or control the last mile HFC network that the client 212 is using to complete the service application.
  • the MSO core network 200 is also shown as including a record keeping server 230 that communicates with the CMTS 222 and the policy server 224.
  • the record keeping server 230 serves a similar function to the billing server 310 described above. Specifically, the record keeping server 230 records the level and amount of QoS that is provided to the clients of each of the service provider's that request specific QoS guarantees on the HFC network of the MSO, e.g., a total number of packets sent/received, an average packet size, an average transmission time, a level of service provided to the packets, etc.). The MSO may then use this information to bill the service provider for the QoS guarantees that have been purchased by the service provider.
  • an MSO may have an exposed policy server 224 that a service provider may access via a COPS-SIP BE 336.
  • the message from the COPS-SIP BE 336 to the policy server may include a request for a QoS guarantee.
  • the policy server 224 may include rules that indicate the cost of the requested QoS guarantee that is relayed back to the service provider via the COPS-SIP BE 336.
  • the service provider may then accept or decline the offered QoS guarantee from the MSO.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)
  • Telephonic Communication Services (AREA)
EP05110241A 2004-11-01 2005-11-01 Système et procédé pour la provision de qualité de service dans une bouble locale Withdrawn EP1655923A3 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US62389904P 2004-11-01 2004-11-01

Publications (2)

Publication Number Publication Date
EP1655923A2 true EP1655923A2 (fr) 2006-05-10
EP1655923A3 EP1655923A3 (fr) 2006-05-17

Family

ID=35920056

Family Applications (1)

Application Number Title Priority Date Filing Date
EP05110241A Withdrawn EP1655923A3 (fr) 2004-11-01 2005-11-01 Système et procédé pour la provision de qualité de service dans une bouble locale

Country Status (3)

Country Link
US (2) US8488612B2 (fr)
EP (1) EP1655923A3 (fr)
CA (1) CA2525050A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103888383A (zh) * 2012-12-24 2014-06-25 华为技术有限公司 资源预留方法、系统及汇聚设备

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI20021378A0 (fi) * 2002-07-12 2002-07-12 Comptel Oyj Menetelmä, välineet ja tietokoneohjelmatuote tietoliikenneyhteyden käytön valvomiseksi ja/tai rajoittamiseksi
US20070124485A1 (en) * 2005-11-30 2007-05-31 Microsoft Corporation Computer system implementing quality of service policy
US7979549B2 (en) * 2005-11-30 2011-07-12 Microsoft Corporation Network supporting centralized management of QoS policies
US20090031394A1 (en) * 2007-07-24 2009-01-29 Telefonaktiebolaget Lm Ericsson (Publ) Methods and systems for inter-resource management service type descriptions
JP5408332B2 (ja) * 2010-03-10 2014-02-05 富士通株式会社 中継装置および通信プログラム
US8156239B1 (en) * 2011-03-09 2012-04-10 Metropcs Wireless, Inc. Adaptive multimedia renderer
US20130304578A1 (en) * 2012-05-08 2013-11-14 24/7 Customer, Inc. Method and apparatus for enhanced in-store retail experience using location awareness
US9621735B2 (en) * 2014-06-25 2017-04-11 Textnow, Inc. Mobile electronic communications combining voice-over-IP and mobile network services
US10516905B2 (en) * 2015-04-01 2019-12-24 Nokia Of America Corporation Dynamic service flow creation for packet cable quality of service guarantee in a distributed cable management system
US11611923B2 (en) * 2018-03-08 2023-03-21 Charter Communications Operatine, LLC Methods and apparatus for supporting quality of service in a system including a cable modem termination system and wireless communications link

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001035604A2 (fr) * 1999-11-05 2001-05-17 Mci Worldcom, Inc. Procede permettant de fournir un service telephonique a protocole internet avec une qualite de service utilisant une signalisation de protocole rsvp point a point
US6553568B1 (en) * 1999-09-29 2003-04-22 3Com Corporation Methods and systems for service level agreement enforcement on a data-over cable system

Family Cites Families (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US950407A (en) * 1907-05-03 1910-02-22 Nicholas Schenk Vehicle-wheel.
US6574216B1 (en) * 1997-03-11 2003-06-03 Verizon Services Corp. Packet data network voice call quality monitoring
US7248682B1 (en) * 1998-12-22 2007-07-24 Cisco Technology, Inc. Dial plan mapper
US6577642B1 (en) * 1999-01-15 2003-06-10 3Com Corporation Method and system for virtual network administration with a data-over cable system
US7296089B2 (en) * 1999-08-27 2007-11-13 At&T Corp. Method for improving web performance by adapting servers based on client cluster characterization
US7369536B2 (en) * 1999-11-02 2008-05-06 Verizon Business Global Llc Method for providing IP telephony with QoS using end-to-end RSVP signaling
US6363065B1 (en) * 1999-11-10 2002-03-26 Quintum Technologies, Inc. okApparatus for a voice over IP (voIP) telephony gateway and methods for use therein
US6760312B1 (en) * 1999-11-30 2004-07-06 Lucent Technologies Inc. Quality of service on demand
US6683853B1 (en) * 1999-12-01 2004-01-27 Telefonaktiebolaget Lm Ericsson (Publ) Dynamic upgrade of quality of service in a packet switched network
US6788696B2 (en) * 2000-03-10 2004-09-07 Nortel Networks Limited Transparent QoS using VC-merge capable access modules
US6961318B2 (en) * 2000-05-12 2005-11-01 International Business Machines Corporation Data transmission system for reserving a virtual connection over multiple IP networks by means of a reservation
US7856497B2 (en) * 2000-05-19 2010-12-21 Mckinnon Iii Martin W Method for determining an appropriate algorithm to apply for forecasting network access usage
US6950407B1 (en) * 2000-09-26 2005-09-27 Mci, Inc. Method and system for providing settlement of interconnected packet-switched networks
US20020075844A1 (en) * 2000-12-15 2002-06-20 Hagen W. Alexander Integrating public and private network resources for optimized broadband wireless access and method
US20030172160A9 (en) * 2001-01-10 2003-09-11 Widegren Ina B. Method and apparatus for coordinating end-to-end quality of service requirements for media flows in a multimedia session
US20020129377A1 (en) * 2001-03-08 2002-09-12 Cloonan Thomas J. Method and apparatus for controlling traffic loading on links between internet service providers and cable modem termination system
US7010305B2 (en) * 2001-03-14 2006-03-07 Nokia Mobile Phones, Ltd. Method for assigning values of service attributes to transmissions, radio access networks and network elements
US7379472B2 (en) * 2001-09-27 2008-05-27 Broadcom Corporation Hardware filtering of unsolicited grant service extended headers
US8040873B2 (en) * 2001-11-07 2011-10-18 Alcatel Lucent Distributed integration of legacy PBX system with SIP networks
EP1331766A1 (fr) * 2001-12-20 2003-07-30 Alcatel Telekommunikationssystem mit einer Architektur von virtuellem Dienst-Netzwerk
JP2003198725A (ja) * 2001-12-28 2003-07-11 Toshiba Corp ケーブルモデム、及びプロトコル変換処理プログラム
US7380022B2 (en) * 2001-12-28 2008-05-27 Motorola, Inc. Method and apparatus for transmitting wired data voice over IP data and wireless data through a common IP core network
US7918734B2 (en) * 2002-09-30 2011-04-05 Time Warner Cable, A Division Of Time Warner Entertainment Company, L.P. Gaming server providing on demand quality of service
US7606156B2 (en) * 2003-10-14 2009-10-20 Delangis Eric M Residential communications gateway (RCG) for broadband communications over a plurality of standard POTS lines, with dynamic allocation of said bandwidth, that requires no additional equipment or modifications to the associated class 5 offices or the PSTN at large
JP4290967B2 (ja) * 2002-11-26 2009-07-08 Ｎｅｃインフロンティア株式会社 無線ＬＡＮネットワークＱｏＳ制御システム、基地局、端末、ＱｏＳ制御方法およびプログラム
WO2004064310A2 (fr) * 2003-01-11 2004-07-29 Omnivergent Communications Corporation Reseau cognitif
US20040160945A1 (en) * 2003-02-13 2004-08-19 Innomedia Pte Ltd. Network communication system with a stand alone multi-media terminal adapter
US7336604B2 (en) * 2003-02-13 2008-02-26 Innomedia Pte Network access module for supporting a stand alone multi-media terminal adapter
US8204042B2 (en) * 2003-05-15 2012-06-19 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for establishing VoIP service in a network
US7480241B2 (en) * 2003-09-02 2009-01-20 Arris International, Inc. Method for processor overload control in a voice over internet protocol cable modem termination system
US7164762B2 (en) * 2003-10-01 2007-01-16 At&T Corp. Enhanced call feature service
US7353279B2 (en) * 2004-01-08 2008-04-01 Hughes Electronics Corporation Proxy architecture for providing quality of service(QoS) reservations
US7609637B2 (en) * 2004-03-03 2009-10-27 Alcatel-Lucent Usa Inc. Network quality of service management
US7522579B1 (en) * 2004-05-03 2009-04-21 Sprint Communications Company Lp Cable system providing SIP-based proxy services
US20060028982A1 (en) * 2004-08-06 2006-02-09 Wright Steven A Methods, systems, and computer program products for managing admission control in a regional/access network based on implicit protocol detection

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6553568B1 (en) * 1999-09-29 2003-04-22 3Com Corporation Methods and systems for service level agreement enforcement on a data-over cable system
WO2001035604A2 (fr) * 1999-11-05 2001-05-17 Mci Worldcom, Inc. Procede permettant de fournir un service telephonique a protocole internet avec une qualite de service utilisant une signalisation de protocole rsvp point a point

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SINNREICH H ET AL: "AAA USAGE FOR IP TELEPHONY WITH QOS" INTERNET DRAFT, January 2001 (2001-01), pages 1-20, XP002939493 *
SINNREICH H ET AL: "Interdomain IP Communications with QoS, Authorization and Usage Reporting" IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, no. 1, February 2000 (2000-02), XP015035436 ISSN: 0000-0004 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103888383A (zh) * 2012-12-24 2014-06-25 华为技术有限公司 资源预留方法、系统及汇聚设备
EP2922258A1 (fr) * 2012-12-24 2015-09-23 Huawei Technologies Co., Ltd. Procédé et système de réservation de ressource, et dispositif de convergence
EP2922258A4 (fr) * 2012-12-24 2015-12-02 Huawei Tech Co Ltd Procédé et système de réservation de ressource, et dispositif de convergence
CN103888383B (zh) * 2012-12-24 2017-09-29 华为技术有限公司 资源预留方法、系统及汇聚设备
US9876733B2 (en) 2012-12-24 2018-01-23 Huawei Technologies Co., Ltd. Resource reservation method and system, and convergence device

Also Published As

Publication number Publication date
EP1655923A3 (fr) 2006-05-17
US20140160989A1 (en) 2014-06-12
US8488612B2 (en) 2013-07-16
US20060104203A1 (en) 2006-05-18
US9100508B2 (en) 2015-08-04
CA2525050A1 (fr) 2006-05-01

Similar Documents

Publication Publication Date Title
US9100508B2 (en) System and method for method for providing quality-of-service in a local loop
US6944166B1 (en) Method for controlling service levels over packet based networks
US6754181B1 (en) System and method for a directory service supporting a hybrid communication system architecture
US7145898B1 (en) System, method and article of manufacture for selecting a gateway of a hybrid communication system architecture
US8194646B2 (en) System and method for providing requested quality of service in a hybrid network
US6909708B1 (en) System, method and article of manufacture for a communication system architecture including video conferencing
US6731625B1 (en) System, method and article of manufacture for a call back architecture in a hybrid network with support for internet telephony
US5867494A (en) System, method and article of manufacture with integrated video conferencing billing in a communication system architecture
US7975037B2 (en) Policy engine in an Internet Protocol multimedia subsystem
US8542592B2 (en) Managing a network flow using application classification information and active signaling relay
US5867495A (en) System, method and article of manufacture for communications utilizing calling, plans in a hybrid network
AU725933C (en) A communication system architecture
US5999525A (en) Method for video telephony over a hybrid network
US6938080B1 (en) Method and computer system for managing data exchanges among a plurality of network nodes in a managed packet network
US8204042B2 (en) Methods, systems, and computer program products for establishing VoIP service in a network
US20070168466A1 (en) Managed Quality of Service Using a Web Server Smart Agent
WO1998034391A9 (fr) Architecture d'un systeme de communication
AU7251198A (en) A system, method and article of manufacture for switched telephony communication
US20060165224A1 (en) Apparatus and method for managing network resources
EP2109275A1 (fr) Procédé et dispositif de commande du nombre de sessions d'un utilisateur
AU6259298A (en) A communication system architecture

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

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK YU

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR MK YU

17P Request for examination filed

Effective date: 20061009

AKX Designation fees paid

Designated state(s): DE FR GB

17Q First examination report despatched

Effective date: 20090526

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: 20091208