WO2007125430A2 - Association d'hôtes à des exigences liées à l'abonné et au service - Google Patents

Association d'hôtes à des exigences liées à l'abonné et au service Download PDF

Info

Publication number
WO2007125430A2
WO2007125430A2 PCT/IB2007/002533 IB2007002533W WO2007125430A2 WO 2007125430 A2 WO2007125430 A2 WO 2007125430A2 IB 2007002533 W IB2007002533 W IB 2007002533W WO 2007125430 A2 WO2007125430 A2 WO 2007125430A2
Authority
WO
WIPO (PCT)
Prior art keywords
subscriber
requirement
host
service
identifier
Prior art date
Application number
PCT/IB2007/002533
Other languages
English (en)
Other versions
WO2007125430A3 (fr
Inventor
Ron E. Haberman
Miroslav Vrana
Joseph M. Regan
Wim Henerickx
Pierre Alfons Leonard Verhelst
Original Assignee
Alcatel Lucent
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 Alcatel Lucent filed Critical Alcatel Lucent
Priority to CN2007800149033A priority Critical patent/CN101433051B/zh
Priority to EP07789679A priority patent/EP2014058A2/fr
Publication of WO2007125430A2 publication Critical patent/WO2007125430A2/fr
Publication of WO2007125430A3 publication Critical patent/WO2007125430A3/fr

Links

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/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H04L12/2869—Operational details of access network equipments
    • H04L12/287—Remote access server, e.g. BRAS
    • H04L12/2876—Handling of subscriber policies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • 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/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • 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/22—Parsing or analysis of headers

Definitions

  • Network service providers e.g., Internet service providers or "ISP"
  • ISP Internet service providers
  • VoIP voice over IP
  • HAI high-speed Internet
  • Edge routing typically is performed at the edge of the provider's core network.
  • An access network aggregates subscriber lines and carries network traffic to and from one or more multi-service edge routers at the provider network edge.
  • DSL digital subscriber line
  • CO telephone company central office
  • Service providers may undertake certain quality of service (QoS) or other commitments, e.g., through a service level agreement (SLA), and may be required or may agree to enforce subscriber specified or other policies, such as access control list (ACL) based or other security policies or requirements.
  • QoS quality of service
  • SLA service level agreement
  • ACL access control list
  • Subscribers vary in terms of the number and type of services to which they subscribe, the number and type of hosts they use to access network services, the number and type of service each host is used to access, whether a residential gateway (RG) or other gateway is present on the subscriber's site (e.g., in their home), and if so whether the gateway is configured as a bridge (each host visible to the access network) or a router (gateway visible to the access network). Therefore, there is a need for an effective way to associate subscriber hosts that connect to a provider network with subscriber and/or service based policies.
  • RG residential gateway
  • Figure IA is a block diagram illustrating an embodiment of a system for associating a subscriber host with subscriber and/or service based requirements.
  • Figure IB is a block diagram illustrating an embodiment of a system for associating a subscriber host with subscriber and/or service based requirements.
  • Figure 1C is a block diagram illustrating an embodiment of a system for associating a subscriber host with subscriber and/or service based requirements.
  • Figure 2 is a block diagram illustrating an embodiment of an access server.
  • Figure 3 is a block diagram illustrating communications associated with configuring a host using the DHCP protocol.
  • Figure 4 is a block diagram illustrating an embodiment of an access server configured to extract data from DHCP lease communications between a subscriber host and a DHCP server and use the extracted data to associate the subscriber host with subscriber and/or service based requirements.
  • Figure 5 is a flow chart illustrating an embodiment of a process for associating a subscriber host with subscriber and/or service based requirements.
  • Figure 6 is a flow chart illustrating an embodiment of a process for using
  • FIG. 7 is a flow chart illustrating an embodiment of a process for associating a subscriber host with subscriber and/or service based requirements.
  • Figure 8 is a flow chart illustrating an embodiment of a process for enforcing a subscriber and/or service based requirement.
  • the invention can be implemented in numerous ways, including as a process, an apparatus, a system, a composition of matter, a computer readable medium such as a computer readable storage medium or a computer network wherein program instructions are sent over optical or electronic communication links.
  • these implementations, or any other form that the invention may take, may be referred to as techniques.
  • a component such as a processor or a memory described as being configured to perform a task includes both a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task.
  • the order of the steps of disclosed processes may be altered within the scope of the invention.
  • the identifier usable to associate a subscriber host with which the lease communication is associated with a subscriber and/or service based requirement.
  • the identifier comprises a string extracted from "option 82" injected into the DHCP lease communications by an access network node, such as a DSLAM in the case of DSL access.
  • the string is mapped to a subscriber and/or service based SLA template or other policy applicable to the host.
  • Multiple hosts associated with the same subscriber and/or used by a single subscriber to access the same service are associated together with a single instance, as applicable, of subscriber and/or service based requirements, as applicable.
  • FIG. IA is a block diagram illustrating an embodiment of a system for associating a subscriber host with subscriber and/or service based requirements.
  • a plurality of subscribers represented in Figure IA by subscribers Sl (102), S2 (104), and Sn (106) access network services via respective DSL connections to an access node, in this example DSLAM 108, e.g., located at a local telephone company central office.
  • the DSLAM 108 provides connectivity via an access server 110 to network services provided via a core provider network to which the access server 110 is connected via a connection 112.
  • access server 110 comprises one or more physical systems and connection 112 represents one or more interfaces and/or connections to the core network.
  • Examples of access server 110 include a multi- service provider edge router, such as the AlcatelTM 7750 service router (SR), one or more aggregation nodes such as the AlcatelTM 7740 Ethernet service switch (ESS), and/or solutions including both the AlcatelTM 7750 SR and the AlcatelTM 7740 ESS.
  • SR AlcatelTM 7750 service router
  • ESS Ethernet service switch
  • each subscriber uses one or more hosts to access services via DSLAM 108 and access server 110.
  • Subscriber Sl (102) uses a single host Hl
  • subscriber S2 (104) uses three hosts H2, H3, and H4 connected to DSLAM 108 via a residential gateway (RG)
  • subscriber Sn (106) uses hosts Hm-I and Hm.
  • the hosts Hl through Hm represented in Figure IA by hosts Hl, H2, H3, H4, Hm-I, and Hm, may be configured in any number of ways.
  • each host associated with a subscriber may be configured to access a particular service (e.g., HSI) or a subscriber may use the " same host to access two or more types of service.
  • a host that uses high speed Internet service (HSI) for general web access may also be used to access video on demand service or VoIP service.
  • HAI high speed Internet service
  • Techniques are known to identify a host that is connecting via an access infrastructure such as the one shown in Figure IA, however, to identify and enforce subscriber based and/or service based policies, service level commitments, and/or other requirements, it is necessary to associate hosts with a subscriber and/or service context, e.g., as described further below.
  • FIG. IB is a block diagram illustrating an embodiment of a system for associating a subscriber host with subscriber and/or service based requirements.
  • a separate virtual circuit VC is configured for each subscriber to enable the traffic associated with that subscriber to be identified.
  • network traffic to/from subscriber Sl (102) represented in Figure IB by the dashed line beginning at host Hl, is associated at the DSLAM 108 with a first virtual circuit VCl. Traffic associated with VCl is tagged with a virtual circuit tag that enables the traffic to be handled correctly.
  • DSLAM 108 uses the virtual circuit tag for traffic associated with VCl to route subscriber bound traffic to the correct subscriber, in this example subscriber Sl (102), and to direct outbound traffic from subscriber Sl to the correct interface/context at access server 110.
  • first virtual circuit VCl is bound to a first service access point SAPl .
  • service access point is used herein to refer to virtual port or other virtual interface configured to provide access to one or more network service, e.g., by processing traffic associated with a particular subscriber and/or multiple subscribers using a particular service.
  • a separate service access point (SAP) has been configured for each subscriber, and the virtual circuit for each subscriber is bound to the corresponding SAP.
  • Subscriber S2 uses hosts H2, H3, and H4 to access network services via an associated residential gateway and a second virtual circuit VC2 bound to SAP2. Traffic associated with second virtual circuit VC2 is indicated by the long-short-long patterned line beginning at hosts H2, H3, and H4. Finally, in this example subscriber Sn (106) uses hosts Hm-I and Hm to access network services via an n-th virtual circuit VCn bound to an n-th service access point SAPn. Traffic associated with n-th virtual circuit VCn is indicated by the dash-dot-dot-dash patterned line beginning at hosts Hm-I and Hm.
  • FIG. 1C is a block diagram illustrating an embodiment of a system for associating a subscriber host with subscriber and/or service based requirements.
  • a virtual circuit and associated service access point is configured for each service, instead of by subscriber as shown in Figure IB.
  • Each subscriber that accesses a service uses the same virtual circuit and associated service access point.
  • there are two services e.g., high speed internet and video on demand), including a first service for which a first virtual circuit VCl and a first service access point SAPl are configured, and a second service for which a second virtual circuit VC2 and a second service access point SAP2 are configured.
  • Traffic associated with the first service is indicated in Figure 1C by the dashed lines beginning at hosts Hl and H2, which in this example are used by subscribers Sl (102) and S2 (104), respectively, to access the first service.
  • Traffic associated with the second service is indicated in Figure 1C by the long- short-long patterned lines beginning at hosts H3, H4, Hm-I, and Hm, which in this example are used by subscribers S2 (104) and Sn (106) to access the second service.
  • a subscriber may use the same host to access two or more services (not shown in Figure 1C), such that traffic from a single host may be spread across service access points, further complicating the task of associating traffic with the correct subscriber and/or service context for purpose of enforcing subscriber and/or service based requirements.
  • Figures IB and 1C show two examples of how an access server may be configured by a provider to provide access to multiple services via a single provider network, e.g., a single IP/MPLS provider core network.
  • a provider network e.g., a single IP/MPLS provider core network.
  • service access points configured on a per subscriber ( Figure IB) or per service ( Figure 1C) basis are shown.
  • Figure IB per subscriber
  • Figure 1C per service
  • other configurations may be used, and it is desirable to provide a way to associate traffic with a subscriber and/or service context, as applicable, to enable subscriber and/or service based requirements to be enforced, regardless of how a particular service provider chooses to configure service access points or similar structures to provide access to network services.
  • Figure 2 is a block diagram illustrating an embodiment of an access server.
  • a first service access point SAPl is configured to provide access to a first service and a second service access point SAP2 is configured to provide access to a second service.
  • the first and second service access points SAPl and SAP2 correspond to the first and second service access points of Figure 1C.
  • Hosts H2, H3, and H4 are shown in this example as being associated with a subscriber context 202 associated with subscriber S2 (106) of Figure 1C.
  • the residential gateway (RG) of Figure 1C is assumed to be configured as a bridge, such that the individual hosts H2, H3, and H4 are visible individually at the access server 110.
  • host H2 is shown as being associated with a first service context (204).
  • each of subscriber context 202 and service contexts 204 and 206 includes an instance of an associated service level agreement (SLA) template configured to enforce subscriber and/or service based requirements, as applicable.
  • SLA service level agreement
  • subscriber based requirements include security requirements, e.g., whether SNMP traffic may be sent to a subscriber's host or whether port 80 (HTTP) requests downstream will be allowed (which may differ for residential and business subscribers, for example), and subscriber (aggregate) or service based quality of service (e.g., speed/bandwidth) commitments.
  • subscriber context 202 and service contexts 204 and 206 include one or more filters determined and/or configured to filter traffic associated with one or more subscriber hosts, e.g., by associating one or more IP addresses with the filter instance based on a determination that the host/IP address is associated with the subscriber and/or the security policy the filter is configured to enforce.
  • one or more of subscriber context 202 and service contexts 204 and 206 include one or more queues and associated scheduler policy instance(s) configured to enforce a QoS or other SLA requirement.
  • subscriber context 202 includes a single scheduler policy instance with which traffic for all hosts associated with the subscriber, in this example hosts H2, H3, and H4, is associated, including if applicable across service access points.
  • DHCP dynamic host configuration protocol
  • many provider networks use the dynamic host configuration protocol (DHCP) to configure hosts to access the provider's network, e.g., by assigning to each host dynamically, at the time a host seeks to connect to the network, an IP address to be used to access the network.
  • DHCP for example, is client/host focused, in the sense that if DHCP or another protocol is used to configure hosts dynamically to access the provider network, host identifying information (e.g., IP address can be determined and used to determine dynamically which host particular traffic is associated with.
  • the DHCP protocol does not provide directly a ready way to associated hosts with a subscriber and/or service context.
  • FIG. 3 is a block diagram illustrating communications associated with configuring a host using the DHCP protocol.
  • the DHCP server 304 sends a DHCP offer to the subscriber host 302, offering use of an IP address specified in the DHCP offer communication for a specified lease period.
  • the subscriber host 302 chooses an offer, if multiple offers have been received, e.g., from multiple DHCP servers, and communicates a DHCP request to the DHCP server that made the offer desired to be accepted, in this example DHCP server 304.
  • the DHCP server 304 sends a DHCP acknowledgement to the subscriber host 302, notifying the subscriber host 302 that it may begin using the IP address indicated in the DHCP request and acknowledgement and may continue to do so for the duration of the specified lease period.
  • an access server such as access server 110 of Figures 1A-2, is located in the path of DHCP lease communications between a subscriber host and a DHCP server.
  • an access server is configured to "snoop" DHCP lease communications as they pass through the access server, or to act as a relay for such communications, thereby enabling the access server to extract from DHCP lease communications information usable to associate a host with a subscriber and/or service context.
  • FIG 4 is a block diagram illustrating an embodiment of an access server configured to extract data from DHCP lease communications between a subscriber host and a DHCP server and use the, extracted data to associate the subscriber host with.. subscriber and/or service based requirements.
  • the access server 110 is configured to monitor DHCP lease communications between subscriber host 302 and DHCP server 304 of Figure 3.
  • the DHCP acknowledgement sent by DHCP server 304 to subscriber host 302 is received and parsed by a DHCP lease communication parser 404 to extract from the DHCP acknowledgement data usable to associate the subscriber host with subscriber and/or service based requirements.
  • parser 404 extracts from the DHCP acknowledgement an IP address assigned to the subscriber host 302 and one or more fields of data, which data is used by parser 404 to generate a string that is then used to identify one or more SLA or other templates indicating subscriber and/or service based requirements to be enforced with respect to the subscriber host 302.
  • a lookup table 406 is used to map the extracted string to an associated subscriber and/or service based SLA template.
  • the SLA template is stored in a profile template database 408, from which the template is retrieve and used to create and configured data structures associated with the subscriber and/or service based requirement (e.g., one or more ingress queues to be used to process inbound traffic from the subscriber host), and to create and/or associate the subscriber host with an instance of a profile configured to enforce the associated subscriber and/or service based requirements (e.g., a scheduler process and/or policy associated with a subscriber with which the subscriber host is associated).
  • the subscriber and/or service based requirement e.g., one or more ingress queues to be used to process inbound traffic from the subscriber host
  • an instance of a profile configured to enforce the associated subscriber and/or service based requirements (e.g., a scheduler process and/or policy associated with a subscriber with which the subscriber host is associated).
  • the parser 404 comprises an embedded Python script processing engine configured, e.g., via a user-defined and/or indicated script, to extract from the DHCP lease communications (e.g., the DHCP acknowledgement) data usable to associate the subscriber host with a subscriber and/or service context.
  • the script comprises one or more regular expressions configured to identify and extract from the DHCP lease communication the data usable to associate the subscriber host with a subscriber and/or service context.
  • the data extracted by parser 404 includes DHCP "option 82" data added by a DSLAM or other access node through which the subscriber host sends/receives DHCP lease .. communications.
  • Option 82 is defined by the DHCP standard specification ' and typically includes a circuit identifier, e.g., indicating the DSLAM port on which the DHCP request was received and a virtual circuit identifier with which the DHCP request is associated.
  • the DHCP server is configured to use option 82 information, e.g., to identify an IP address pool from which to assign an IP address to the requesting host.
  • DSLAM physical port information is extracted from the option 82 data and mapped (either directly or by generating a string based thereon), e.g., using a lookup table such as table 406 of Figure 4, to a subscriber identifier that in turn is used as a key to find, in a policy template database such as database 408 of Figure 4, one or more subscriber and/or service based requirements to be enforced with respect to the subscriber host.
  • the approach described above and shown in Figure 4 makes it unnecessary to provision the access server on a per subscriber basis to enforce subscriber and/or service based requirements.
  • a set of predefined templates are stored and for each subscriber one or more entries are included in table 406 to map a subscriber identifier and/or one or more service identifiers extracted from DHCP lease communication to one or more corresponding profiles (e.g., SLA templates) to be applied with respect to the subscriber hosts associated with the subscriber and/or the host(s) used by the subscriber to access a particular service.
  • profiles e.g., SLA templates
  • Figure 5 is a flow chart illustrating an embodiment of a process for associating a subscriber host with subscriber and/or service based requirements.
  • the process of Figure 5 is implemented on a multi-service edge router, such as the access router 110 of Figures 1 A-2 and 4.
  • a DHCP acknowledgement is received (502).
  • 502 includes monitoring DHCP lease communications between a subscriber host and a DHCP server. Data usable to associate a subscriber host with which the DHCP acknowledgement is associated with a subscriber and/or service based requirement is extracted from the DHCP acknowledgement (504).
  • 504 includes parsing the DHCP acknowledgement and generating, based at least in part on option 82 and/or other data comprising the DHCP acknowledgement, a string usable to identify a subscriber and/or service profile usable to associate the subscriber host with a subscriber and/or service based requirement.
  • 504 includes using a string extracted from the DHCP acknowledgement to perform a lookup in a table such as table 406, and using a subscriber (or other) identifier read from the table to create an instance of a subscriber and/or service based policy and associate the subscriber host with the newly created policy (e.g., by associating the IP address assigned to the subscriber host with the policy instance) and/or to associate the subscriber host with an existing policy instance, e.g., an instance created and associated previously with one or more other hosts associated with the same subscriber and/or used by a subscriber to access the same service. Applicable subscriber and/or service based policies subsequently are enforced with respect to the subscriber host (506).
  • Figure 6 is a flow chart illustrating an embodiment of a process for using
  • DHCP lease communication data to associate a subscriber host with subscriber and/or service based requirements.
  • 504 of Figure 5 includes the process of Figure 6.
  • a DHCP acknowledgement (or other DHCP lease communication) is parsed (604).
  • 604 includes parsing type-length-value fields included in the DHCP acknowledgement to extract one or more name-value pairs.
  • One or more policy (e.g., SLA) template identifier strings are extracted from the parsed DHCP acknowledgement data (606).
  • at least one identifier extracted in 606 comprises a subscriber identifier associated uniquely with a subscriber with which the subscriber host to which the DHCP acknowledgement pertains.
  • the identifier string is mapped to one or more subscriber and/or service based policies (e.g., profiles and/or templates) to be enforced with respect to the subscriber host to which the DHCP acknowledgement pertains.
  • 606 includes consulting a lookup table such as table 406 of Figure 4.
  • 606 includes using the result of such a lookup to associate the subscriber host with a new and/or previously created instance of an applicable policy.
  • Figure 7 is a flow chart illustrating an embodiment of a process for associating a subscriber host with subscriber and/or service based requirements.
  • 606 of Figure 6 includes the process of Figure 7.
  • a string extracted from a DHCP lease communication (e.g., DHCP acknowledgement) is used to look up one or more policy identifiers (702), e.g., from a lookup table such as table 406 of Figure 4.
  • the policy identifier(s) is/are used to associate the subscriber host with a new and/or previously created instance(s) of one or more applicable policies (704), e.g., by using the identifier determined at 702 to retrieve the applicable policy from a policy database such as database 408 of Figure 4.
  • 702 includes associating the subscriber host with a subscriber profile and 704 includes retrieving the subscriber profile and/or one or more policies associated with the subscriber profile.
  • Figure 8 is a flow chart illustrating an embodiment of a process for enforcing a subscriber and/or service based requirement.
  • the process of Figure 8 is used to enforce an aggregate QoS or other subscriber based requirement with respect to one or more hosts associated with a particular subscriber.
  • a queue e.g., an ingress queue
  • 802 includes binding an IP address assigned to one or more subscriber hosts to an ingress or other queue associated with a subscriber with which the one or more subscriber hosts are associated.
  • a scheduler policy is associated with the queue (804).
  • the scheduler policy determines at least in part how/when packets are pulled from the ingress queue configured at 802 and processed.
  • a single instance of a scheduler policy is configured to enforce an aggregate QoS or other subscriber base SLA commitment and all hosts associated with a particular subscriber are linked to the single scheduler policy instance.
  • one or more service based requirements may also be required to be enforced, and one or more hosts used by a particular subscriber to access a particular service may be bound to a policy instance configured to enforce the service based requirement.
  • traffic received from one or more subscriber hosts associated with the subscriber for which the queue was configured in 802 is associated with (e.g., place in) the queue configured in 802, e.g., on the basis of assigned IP address, and packets are pulled from the queue and processed in accordance with the aggregate scheduler policy associated with the queue at 804.
  • subscriber and/or service based requirements include, without limitation, using DHCP lease communication data to enforce security requirements, e.g., by adding dynamically to an ACL or other filter an IP address assigned to a subscriber host, and enforcing per service QoS and/or other SLA commitments applicable to those hosts used by a particular subscriber to access a particular service.
  • a single host may be configured to access two or more services, or a routed residential gateway may result in multiple hosts each used to access a different network service appearing to the network as a single host (i.e., the residential gateway) accessing multiple services.
  • such hosts are associated with more complicated SLA templates that enable any service based requirements, if any, applicable to a particular service to be enforced with respect to traffic associated with that service.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

Cette invention traite de l'association d'hôtes à des exigences liées à l'abonné et au service. Un identifiant est extrait d'une communication de location de protocole DHCP ou d'autre adresse réseau, associée à un hôte abonné. L'identifiant est utilisé pour associer l'hôte abonné à une exigence liée à l'abonné et/ou au service. L'hôte abonné appartient à un ensemble d'un ou plusieurs hôtes abonnés associés à l'abonné et/ou au service, selon l'usage requis, laquelle exigence doit être mise en oeuvre collectivement auprès du ou des hôtes abonnés de l'ensemble.
PCT/IB2007/002533 2006-04-27 2007-04-27 Association d'hôtes à des exigences liées à l'abonné et au service WO2007125430A2 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN2007800149033A CN101433051B (zh) 2006-04-27 2007-04-27 将主机与基于用户和服务的需求相关联的方法和设备
EP07789679A EP2014058A2 (fr) 2006-04-27 2007-04-27 Association d'hôtes à des spécifications fondées sur l'abonné et le service

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/414,725 US8416691B1 (en) 2006-04-27 2006-04-27 Associating hosts with subscriber and service based requirements
US11/414,725 2006-04-27

Publications (2)

Publication Number Publication Date
WO2007125430A2 true WO2007125430A2 (fr) 2007-11-08
WO2007125430A3 WO2007125430A3 (fr) 2008-04-03

Family

ID=38655885

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2007/002533 WO2007125430A2 (fr) 2006-04-27 2007-04-27 Association d'hôtes à des exigences liées à l'abonné et au service

Country Status (4)

Country Link
US (1) US8416691B1 (fr)
EP (1) EP2014058A2 (fr)
CN (1) CN101433051B (fr)
WO (1) WO2007125430A2 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009078765A1 (fr) * 2007-12-17 2009-06-25 Telefonaktiebolaget Lm Ericsson Procédé et agencement pour une qualité de service de réseau
WO2009085787A1 (fr) * 2007-12-21 2009-07-09 General Instrument Corporation Gestion d'une largeur de bande lors d'une période sans collision dans un rle
WO2010098705A1 (fr) * 2009-02-26 2010-09-02 Telefonaktiebolaget Lm Ericsson (Publ) Configuration de politique de bande passante spécifique de service dans des réseaux de données
EP2439903A1 (fr) * 2010-10-08 2012-04-11 Huawei Technologies Co., Ltd. Procédé de fourniture d'informations, passerelle domestique et système de réseau domestique
EP2451125A1 (fr) * 2009-07-28 2012-05-09 ZTE Corporation Procédé et système d exécution de découverte de topologie de réseau

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103428025A (zh) * 2012-05-25 2013-12-04 中兴通讯股份有限公司 一种管理虚拟网络服务的方法、装置和系统
DE102013114069A1 (de) * 2013-01-03 2014-07-03 Samsung Electronics Co., Ltd. Rekonfigurierbare Speichervorrichtung
US10505891B2 (en) 2015-04-02 2019-12-10 Nicira, Inc. Security policy selection for machines with dynamic addresses
US10200342B2 (en) 2015-07-31 2019-02-05 Nicira, Inc. Dynamic configurations based on the dynamic host configuration protocol
US11606333B1 (en) 2022-03-04 2023-03-14 Cisco Technology, Inc. Synchronizing dynamic host configuration protocol snoop information

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6223222B1 (en) * 1998-05-14 2001-04-24 3Com Corporation Method and system for providing quality-of-service in a data-over-cable system using configuration protocol messaging
US20030182666A1 (en) * 2002-03-19 2003-09-25 Gang-Jae You Service-quality management system for asymmetric digital subscriber line
US6876667B1 (en) * 2001-04-30 2005-04-05 Cisco Technology, Inc. Method and apparatus for establishing class of service configuration in a network device of a broadband cable network using dynamic host configuration protocol

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6577628B1 (en) * 1999-06-30 2003-06-10 Sun Microsystems, Inc. Providing quality of service (QoS) in a network environment in which client connections are maintained for limited periods of time
US20020065907A1 (en) * 2000-11-29 2002-05-30 Cloonan Thomas J. Method and apparatus for dynamically modifying service level agreements in cable modem termination system equipment
US7352853B1 (en) * 2001-05-22 2008-04-01 Cisco Technology, Inc. Automation of customer premises equipment provisioning in a telecommunications network
US7106739B2 (en) * 2001-06-27 2006-09-12 Intel Corporation Method enabling network address translation of incoming session initiation protocol connections based on dynamic host configuration protocol address assignments
US6801528B2 (en) * 2002-07-03 2004-10-05 Ericsson Inc. System and method for dynamic simultaneous connection to multiple service providers
US7260639B2 (en) * 2002-07-09 2007-08-21 Akamai Technologies, Inc. Method and system for protecting web sites from public internet threats
US7337224B1 (en) * 2002-10-24 2008-02-26 Cisco Technology, Inc. Method and apparatus providing policy-based determination of network addresses
US7249187B2 (en) * 2002-11-27 2007-07-24 Symantec Corporation Enforcement of compliance with network security policies
KR100694045B1 (ko) * 2003-10-23 2007-03-12 삼성전자주식회사 ＤＨＣＰｖ4 환경하에서의 핸드오버 방법, 핸드오버 장치및 상기 핸드오버 방법이 저장된 정보저장매체
CA2457368C (fr) * 2004-02-11 2013-01-08 Solutioninc Limited Serveur, systeme et methode offrant l'acces a un reseau public par l'intermediaire d'un reseau interne d'un operateur multisystemique
US7020090B2 (en) * 2004-06-21 2006-03-28 Cisco Technology, Inc. System and method for loadbalancing in a network environment using feedback information
US7860019B2 (en) * 2004-11-05 2010-12-28 Toshiba America Research, Inc. Peer-to-peer network and user information discovery and sharing for mobile users and devices
GB2425681A (en) * 2005-04-27 2006-11-01 3Com Corporaton Access control by Dynamic Host Configuration Protocol snooping
KR100738526B1 (ko) * 2005-06-02 2007-07-11 삼성전자주식회사 다중 영구가상회선 접속환경을 위한 중간 인증관리 시스템및 그 방법
US9088619B2 (en) * 2005-09-14 2015-07-21 Cisco Technology, Inc. Quality of service based on logical port identifier for broadband aggregation networks
WO2007071004A1 (fr) * 2005-12-20 2007-06-28 Bce Inc. Appareil et procede pour prendre en charge des categories de trafic multiples au niveau d'un seul dispositif en reseau

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6223222B1 (en) * 1998-05-14 2001-04-24 3Com Corporation Method and system for providing quality-of-service in a data-over-cable system using configuration protocol messaging
US6876667B1 (en) * 2001-04-30 2005-04-05 Cisco Technology, Inc. Method and apparatus for establishing class of service configuration in a network device of a broadband cable network using dynamic host configuration protocol
US20030182666A1 (en) * 2002-03-19 2003-09-25 Gang-Jae You Service-quality management system for asymmetric digital subscriber line

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101904133A (zh) * 2007-12-17 2010-12-01 爱立信电话股份有限公司 用于网络qos的方法和装置
WO2009078765A1 (fr) * 2007-12-17 2009-06-25 Telefonaktiebolaget Lm Ericsson Procédé et agencement pour une qualité de service de réseau
CN101904133B (zh) * 2007-12-17 2016-09-07 爱立信电话股份有限公司 用于网络qos的方法和装置
US9054966B2 (en) 2007-12-17 2015-06-09 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement for network QoS
US8650294B2 (en) 2007-12-17 2014-02-11 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement for network QoS
WO2009085787A1 (fr) * 2007-12-21 2009-07-09 General Instrument Corporation Gestion d'une largeur de bande lors d'une période sans collision dans un rle
WO2010098705A1 (fr) * 2009-02-26 2010-09-02 Telefonaktiebolaget Lm Ericsson (Publ) Configuration de politique de bande passante spécifique de service dans des réseaux de données
US9331914B2 (en) 2009-02-26 2016-05-03 Telefonaktiebolaget L M Ericsson (Publ) Service specific bandwidth policy configuration in data networks
EP2401843A4 (fr) * 2009-02-26 2015-04-29 Ericsson Telefon Ab L M Configuration de politique de bande passante spécifique de service dans des réseaux de données
EP2451125A4 (fr) * 2009-07-28 2014-07-02 Zte Corp Procédé et système d exécution de découverte de topologie de réseau
EP2451125A1 (fr) * 2009-07-28 2012-05-09 ZTE Corporation Procédé et système d exécution de découverte de topologie de réseau
EP2439903A1 (fr) * 2010-10-08 2012-04-11 Huawei Technologies Co., Ltd. Procédé de fourniture d'informations, passerelle domestique et système de réseau domestique
US8606937B2 (en) 2010-10-08 2013-12-10 Huawei Technologies Co., Ltd. Information providing method, home gateway, and home network system
KR101319418B1 (ko) 2010-10-08 2013-10-17 후아웨이 테크놀러지 컴퍼니 리미티드 정보 제공 방법, 홈 게이트웨이 및 홈 네트워크 시스템
EP2439903A4 (fr) * 2010-10-08 2013-01-23 Huawei Tech Co Ltd Procédé de fourniture d'informations, passerelle domestique et système de réseau domestique
JP2013500653A (ja) * 2010-10-08 2013-01-07 ▲ホア▼▲ウェイ▼技術有限公司 情報を提供するための方法、ホームゲートウェイおよびホームネットワークシステム

Also Published As

Publication number Publication date
CN101433051B (zh) 2013-01-30
US8416691B1 (en) 2013-04-09
WO2007125430A3 (fr) 2008-04-03
EP2014058A2 (fr) 2009-01-14
CN101433051A (zh) 2009-05-13

Similar Documents

Publication Publication Date Title
US8416691B1 (en) Associating hosts with subscriber and service based requirements
US8121126B1 (en) Layer two (L2) network access node having data plane MPLS
US7411975B1 (en) Multimedia over internet protocol border controller for network-based virtual private networks
AU2010255430B2 (en) Dynamically configuring attributes of a parent circuit on a network element
US8675488B1 (en) Subscriber-based network traffic management
US7539193B2 (en) System and method for facilitating communication between a CMTS and an application server in a cable network
TWI520639B (zh) 動態地產生服務群組之方法、裝置與系統
US8854974B2 (en) Methods, systems, and computer readable media for deep packet inspection (DPI)-enabled traffic management for xDSL networks
US8681779B2 (en) Triple play subscriber and policy management system and method of providing same
KR101458779B1 (ko) 콘텐트 기반 브리징을 지원하기 위한 이더넷 네트워크에 대한 콘텐트 기반 ｖｌａｎ 분류 및 프레임워크
JP2006515124A (ja) ネットワーク装置の動的ポート・コンフィギュレーション
WO2004107671A1 (fr) Dispositif de communication
US8072978B2 (en) Method for facilitating application server functionality and access node comprising same
CA2774281C (fr) Procede d'acces utilisateur, systeme et serveur d'acces, dispositif d'acces
US7460536B1 (en) User and session identification based on connections, protocols and protocol fields
EP3836487A1 (fr) Système, dispositif et procédé de gestion de comportement d'accès internet
EP2157735A1 (fr) Procédé, système de communication et équipement apparenté pour localiser une ressource d'utilisateur
KR100508405B1 (ko) 사설 서브-네트웍 검출장치 및 검출방법
JP2002118588A (ja) レルム名又はドメイン名による通信サービス条件制御方法
TWI415425B (zh) The home network gateway provides a domain name assignment method for multiple WAN connections
WO2014161315A1 (fr) Procédé et système de gestion de réseau basés sur un modèle d'information commun

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2007789679

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 200780014903.3

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE