WO2006042464A1 - A method for achieving the service connection resource management - Google Patents

A method for achieving the service connection resource management Download PDF

Info

Publication number
WO2006042464A1
WO2006042464A1 PCT/CN2005/001714 CN2005001714W WO2006042464A1 WO 2006042464 A1 WO2006042464 A1 WO 2006042464A1 CN 2005001714 W CN2005001714 W CN 2005001714W WO 2006042464 A1 WO2006042464 A1 WO 2006042464A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer network
resource
resource manager
connection
request
Prior art date
Application number
PCT/CN2005/001714
Other languages
French (fr)
Chinese (zh)
Inventor
Yuepeng Chen
Lingyuan Fan
Dengchao Wu
Bo Xu
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2006042464A1 publication Critical patent/WO2006042464A1/en

Links

Classifications

    • 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/80—Responding to QoS

Definitions

  • the present invention relates to resource management technologies, and more particularly to a method for implementing service connection resource management. Background of the invention
  • FIG. 1 shows a Diff-serv model with an independent bearer control layer.
  • the bearer control layer 102 is disposed between the bearer network 103 and the service control layer 101.
  • the call agent (CA, Call Agent) in the service control layer 101 is a service server, such as a soft switch, and the like, and can be sold as a soft switch.
  • the bearer control layer 102 one or more bearers are included.
  • the network resource manager, the bearer network resource manager is responsible for configuring the management rules and the network topology, and allocating resources for the customer's service bandwidth request, and controlling and managing the service bandwidth request requests of the respective bearer network resource managers through signaling. And the result, and the routing path information allocated for the service request, for example: controlling and managing the communication between the bearer network resource manager 1, the bearer network resource manager 2, and the bearer network resource manager 3; in the bearer network 103,
  • Each bearer network resource manager manages a specific bearer network area.
  • This specific bearer network area is called the management domain of the corresponding bearer network resource manager, for example: the management domain 105 of the bearer network resource manager 1, and the bearer.
  • ER edge router
  • BR border router
  • CN connection node
  • the bearer network resource manager is configured with management rules and network topology to allocate resources for the customer's service bandwidth request.
  • the bearer network resource manager determines the path of the user service and notifies the edge router to forward the service flow according to the specified path.
  • the bearer network implements the user service flow forwarding according to the specified route according to the path determined by the bearer control layer.
  • the industry mainly uses the MPLS technology to establish an LSP along the service flow path specified by the bearer control layer by using the resource reservation mode, using RSVP-TE or The CR-LDP display routing mechanism establishes an end-to-end LSP.
  • FIG. 2 the specific processing flow for realizing the service connection resource allocation is as shown in FIG. 2, which includes the following steps:
  • Step 201 The calling CA sends a connection resource request to the bearer network resource manager connected thereto.
  • the bearer network resource manager connected to the calling CA is referred to as a source bearer network resource manager.
  • Steps 202 to 204 The bearer network resource manager that receives the connection resource request determines whether it is the destination bearer network resource manager of the current service connection. If not, the bearer network resource manager determines the local information according to the address information in the connection resource request. Domain ingress router and egress router, and The routing algorithm is used to perform intra-domain and inter-domain routing, and the corresponding path resource information is recorded. At the same time, the bearer network resource manager forwards the connection resource request to the downstream bearer network resource manager, and returns to the step.
  • step 205 go to step 205.
  • the bearer network resource manager is determined according to the ER access information saved by the ER access information and the identity information of the calling UE in the connection resource request, and the UE identity information may be an IP address or a domain name information, and the IP address is carried in the IP address.
  • the five-tuple of the connection resource request is determined according to the ER access information saved by the ER access information and the identity information of the calling UE in the connection resource request, and the UE identity information may be an IP address or a domain name information, and the IP address is carried in the IP address. The five-tuple of the connection resource request.
  • the bearer network resource manager can determine the downstream bearer network resource manager by using the LSP information of the bearer network and the routing information of each CN, and can also determine the downstream bearer network resource manager by using the two information and signaling routing algorithms.
  • Step 205 The destination bearer network resource manager completes the service routing and the LSP resource allocation, and delivers the QoS policy to the router corresponding to the selected routing path in the domain, and then returns the connection resource response to the up-hop bearer network resource manager.
  • Steps 206 to 208 The bearer network resource manager that receives the connection resource response completes its own service routing and LSP resource allocation, and delivers a QoS policy to the router corresponding to the selected routing path in the domain, and then determines whether it is the source bearer network.
  • the resource manager if yes, ends the processing flow, otherwise, returns a connection resource response to its own previous hop bearer network resource manager, and then returns to step 206.
  • the bearer network resource manager determines the routing path and allocates the corresponding resource
  • the determined QoS policy is sent to the routing device in the bearer network, but this A plurality of communication channels are required to be established between the bearer control layer and the bearer network device for carrying the interaction between the network resource manager and the routing device. Therefore, not only the resource overhead of the bearer network system but also the operational load of the bearer network is increased. And increase the complexity of the entire system processing.
  • the bearer control layer and the bearer network are two independent layers, and the network devices in each layer are also independent of each other. Therefore, if the network device and the bearer network used by the bearer control layer are used, If the device does not belong to the same manufacturer, there are still problems in the mutual support between the two network devices. If some functions, such as ensuring that QoS functions cannot support each other, but require two layers of devices to perform this function, they must interact. It is possible that the QoS of the service connection in the entire system cannot be guaranteed. Summary of the invention
  • the main object of the present invention is to provide a method for implementing service connection resource management, which can reduce system resource overhead and operation load, and can ensure QoS of each service flow of the entire system.
  • a method for implementing service connection resource management comprising the following steps:
  • the call proxy After receiving the service connection request of the calling user, the call proxy sends a connection resource request to the source bearer network resource manager;
  • the bearer network resource manager that receives the connection resource request performs intra-domain and inter-domain routing, applies for and records the intra-domain and inter-domain path resources, and determines whether it is the destination bearer network resource manager. If yes, step c is performed. Otherwise, the current bearer network resource manager forwards the connection resource request to the next hop bearer network resource manager, and returns to step b;
  • the QoS policy is not sent to the bearer network routing device, and the connection resource response is immediately returned to the bearer network resource manager until the connection resource response is sent to the source bearer network resource manager.
  • Step b further includes: each bearer network resource manager determines the ingress router in the domain according to the address information in the connection resource request, and then uses the routing algorithm to perform intra-domain and inter-domain routing according to the determined ingress router. And determine the egress router in this domain.
  • the connection resource response carries the path resource of the current bearer network resource manager and the path resource returned by the current bearer network resource manager next hop bearer network resource manager.
  • each bearer network resource manager stores a bearer network managed by itself. Topology and full resource information.
  • the topology and resource information of the bearer network are obtained through configuration according to the actual situation of the network; or dynamically collected through a traffic engineering-based routing protocol or an SNMP protocol, or obtained by extending the COPS standard protocol.
  • the method further includes: synchronizing the data information on the corresponding bearer network resource manager.
  • the bearer network is an IP network, or an MPLS network, or an ATM network.
  • the path resource is a label switched path, or a tunnel, or a permanent virtual circuit, or an switched virtual circuit.
  • the connection resource request is a service request request, or a service modification request, or a service release request.
  • the method for implementing the service connection resource management removes the step of the bearer network resource manager transmitting the QoS policy to the bearer network device, and the destination bearer network resource manager directly performs the uplink hop after the service route and the path resource allocation are completed.
  • the network resource manager returns a response, and the source inherits the response from the previous hop until the source hosts the network resource manager. In this way, it is not necessary to establish a communication channel between the bearer control layer and the bearer network routing device for downlink QoS policy and the like, thereby reducing the resource overhead of the bearer network system, reducing the running load of the bearer network, and reducing the operation load.
  • the complexity of the entire system processing is not necessary to establish a communication channel between the bearer control layer and the bearer network routing device for downlink QoS policy and the like, thereby reducing the resource overhead of the bearer network system, reducing the running load of the bearer network, and reducing the operation load. The complexity of the entire system processing.
  • the bearer control layer does not need to cooperate with the routing device of the bearer network, even if devices of different vendors are used at two levels, the QoS of the service connection will not be affected, and the QoS of the entire system can be fully guaranteed, and the Differ-serv model is solved. It is not possible to provide QoS guarantee for each service flow, which is convenient for commercial networks of various sizes.
  • the method of the present invention can be applied to various bearer networks, such as an IP network including an MPLS network, an ATM network, and other types of bearer networks.
  • the corresponding path may be LSP, tunnel PVC, SVC, etc.
  • the invention has wider application range, more practicality and more flexible use. Since the existing bearer network device already supports the dynamic routing protocol, the SNMP protocol, and the like, the present invention has little change to the bearer network and is easy to implement.
  • FIG. 1 is a schematic diagram of a network model of an independent bearer control layer in the prior art
  • FIG. 3 is a flowchart of processing for implementing service connection resource management according to the present invention. Mode for carrying out the invention
  • the core idea of the present invention is: After receiving the resource request sent by the service control layer, the source bearer network resource manager completes its own service route and path resource allocation, and forwards the connection resource request to the next hop until the destination bearer network
  • the resource manager each bearer network resource manager that receives the connection resource request completes its own service route and path resource allocation; after the destination bearer network resource manager completes the service route and the path resource assignment, immediately forwards the network resource to the next hop.
  • the manager returns a connection resource response until the source hosts the network resource manager without sending a QoS policy to the bearer network device.
  • the connection resource response carries path resource information of the own and its next hop bearer network resource manager.
  • each bearer network resource manager stores topology information and all resource information of the bearer network managed by itself, and the path for obtaining the saved information may be manually configured according to actual application conditions of the network; It is collected through existing routing protocols based on traffic engineering or SNMP protocol, or extended by standard protocols such as COPS.
  • the data information in the bearer network resource manager corresponding to the changed bearer network is updated synchronously; if the service connection is already carried, the corresponding fault processing is performed.
  • the call agent that connects or notifies the service control layer can be directly removed, and the call agent decides what to do.
  • the service call agent When the service call agent establishes a service connection, it needs to send a check to the bearer network resource manager.
  • Request resource requests such as: query bandwidth parameters, other QoS parameters, etc.
  • the bearer network resource manager performs routing and resource calculation according to the specific topology of the network and the QoS requirements of the service connection, and responds to the service call agent. If the required QoS policy is met, the service connection can be established. Otherwise, the service connection cannot be established.
  • the bearer network resource manager may return a response to the service control layer; otherwise, the resource request needs to be sent to the other On the bearer network resource manager, each bearer network resource manager performs corresponding topology and resource calculation, and finally returns the result to the call agent that initiates the service connection resource request.
  • the bearer network in the present invention may be an IP network including an MPLS network, an ATM network, or another type of bearer network. Therefore, the corresponding path may be a label switched path (LSP), a tunnel, or a permanent virtual circuit. (PVC), switched virtual circuit (SVC), etc.
  • LSP label switched path
  • PVC permanent virtual circuit
  • SVC switched virtual circuit
  • connection resource request in the present invention may be a service application request, or a service modification request, or a service release request.
  • the specific processing procedure of the present invention includes the following steps:
  • Step 301 After receiving the service connection request of the calling user, the call agent sends a connection resource request to the bearer network resource manager connected thereto; the bearer network resource manager saves the connection information for the current service flow.
  • the bearer network resource manager connected to the call agent is called the source bearer network resource manager
  • the bearer network resource manager to which the called user belongs is called the destination bearer network resource manager, the source bearer network resource manager and the destination bearer network.
  • the bearer network resource manager between resource managers is called an intermediate bearer network resource manager.
  • Step 302 The bearer network resource manager that receives the connection resource request determines the ingress router of the own management domain according to the source IP address of the quintuple in the connection resource request.
  • the source bearer network resource manager For the source bearer network resource manager, it is based on the source IP address of the quintuple in the connection resource request. The address determines which ER the source IP address belongs to.
  • the ingress BR of the local domain is determined according to the IP address carried in the connection resource request.
  • the hop-by-hop routing algorithm selects the inter-domain path by the previous hop bearer network resource manager, according to The path can determine the ingress router of the domain and the egress router of the management domain of the previous hop bearer network resource manager.
  • Step 303 The current bearer network resource manager uses the service routing algorithm to perform intra-domain routing in its own management domain, apply for intra-domain path resources, and record the path resource information.
  • any existing intra-domain routing algorithm can be used to implement intra-domain routing, such as: Dijakstra algorithm, Bdlman-Ford algorithm, static configuration algorithm, or matrix routing table method.
  • Step 304 The current bearer network resource manager uses the signaling routing algorithm to perform inter-domain routing between itself and the next hop carrier network resource manager to determine an egress router in the domain.
  • any existing inter-domain routing algorithm can be used to implement inter-domain routing, such as hop-by-hop routing, forward-constrained reverse routing, and so on.
  • Steps 305-306 The current bearer network resource manager determines whether it is the destination bearer network resource manager. If yes, step 307 is performed; otherwise, the current bearer network resource manager forwards the connection resource to the next-hop bearer network resource manager. The request returns to step 302.
  • Step 307 The destination bearer network resource manager completes service routing and path resource allocation, and then returns a connection resource response to the uplink hop bearer network resource manager.
  • the bearer network resource manager does not deliver the QoS policy to the routing device of the bearer network.
  • Step 308 The bearer network resource manager that receives the connection resource response returns the connection resource response to the up-hop bearer network resource manager, and repeats this step until the source bearer network resource manager.
  • connection resource response carries its own path resource information and the F-hop resource information returned by the bearer network resource manager.
  • Step 309 The source bearer network resource manager returns the routing and path resource information to the calling proxy that initiated the request.
  • the present invention does not need to carry the bearer network resource manager of the control layer to deliver the routing device to the bearer network.
  • the QoS policy is configured to dynamically collect the mapping structure information and resource information of the bearer network, generate mapping information for dynamic allocation of service connection resources, and perform routing and resource calculation through traffic engineering, thereby ensuring The QoS of the service connection in the bearer network.
  • a bearer network resource manager can collect topology information and resource information from a bearer network through a protocol such as SNMP.
  • the bearer network resource manager puts the collected information into its own database;
  • the bearer network resource manager performs routing according to a traffic management policy configured in advance, such as a minimum delay principle or a minimum cost principle, and performs calculation of bandwidth and other resources.
  • the bearer network resource The manager continues to apply to its own downstream bearer network resource manager or feeds back the results to its own upstream bearer network resource manager. In this way, the QoS of the service connection in the bearer network can be guaranteed.

Abstract

A method was disclosed for achieving the service connection resource management, which comprises the steps: a. The Call agent sends the connection resource request to the source bearing network resource manager after it receives the service connection request of the calling user; b. The bearing network resource manager which received the connection resource request selects the route within the domain and between the domains, and applies and records the path resource within the domain and between the domains, as well as judges if itself is the destination bearing network resource manager, if so, perform the step c; or else, return the step b when the current bearing network resource manager forwards the connection resource request to next hop bearing network resource manager; c. Return the connection resource response immediately after achieving the service routing and path resource assignment, without sending the QoS policy to the bearing network routing device, until sending the connection resource response to the source bearing network resource manager. Present method can reduce the system resource overhead and the operation load, and ensure the QoS of each service stream in the whole system.

Description

一种实现业务连接资源管理的方法 技术领域  Method for realizing business connection resource management
本发明涉及资源管理技术， 尤指一种实现业务连接资源管理的方法。 发明背景  The present invention relates to resource management technologies, and more particularly to a method for implementing service connection resource management. Background of the invention
随着互联网规模的不断扩大， 各种各样的网络服务争相涌现， 先进的 多媒体***也层出不穷。 由于实时业务对网络传输时延、 延时抖动等特性 较为敏感， 当网络上有突发性高的文件传输（FTP )或含有图像文件的超文 本传输（HTTP )等业务时， 实时业务就会受到很大影响； 另外， 由于多媒 体业务将占用大量的带宽， 所以也将使得现有网络中需要得到保证的关键 业务难以得到可靠的传输。 于是， 为保证关键业务得到可靠的传输， 各种 服务质量（QoS, Quality of Service )技术便应运而生。 互联网工程任务组 With the continuous expansion of the Internet, a variety of network services have emerged, and advanced multimedia systems have emerged. Since the real-time service is sensitive to network transmission delay and delay jitter, when there is a sudden high file transfer (FTP) or hypertext transfer (HTTP) containing image files, the real-time service will It is greatly affected; in addition, because multimedia services will occupy a large amount of bandwidth, it will also make it difficult to obtain reliable transmission of critical services that need to be guaranteed in existing networks. Therefore, in order to ensure reliable transmission of key services, various quality of service (QoS) technologies have emerged. Internet Engineering Task Force
( IETF, Internet Engineering Task Force ) 已经提出了很多服务模型和机制 , 以满足 QoS的需求。 目前业界比较认可的是在网络的接入或边缘使用综合 业务 （Int-Serv， Integrated Service )模型， 而在网络的核心使用区分业务(IETF, Internet Engineering Task Force) has proposed a number of service models and mechanisms to meet the needs of QoS. At present, the industry is more recognized in the network access or edge use integrated services (Int-Serv, Integrated Service) model, and the use of differentiated services in the core of the network
( Diff-serv, Differentiated Service )模型。 (Diff-serv, Differentiated Service) model.
由于 Diff-serv模型仅通过设定优先级的方式来保障 QoS， 效果难以预 测。 因此， 业界为骨干网的 Diff-Serv模型引入了一个独立的承载控制层， 建立了专门的 Diff-Serv QoS信令机制，并利用 Diff-Serv网络新增的承载控 制层管理网络的拓朴资源， 这种 Diff-Serv 被称为有独立承载控制层的 Diff-Serv模型， 图 1为有独立承载控制层的 Diff-serv模型图。 如图 1所示， 在该模型中， 承载控制层 102设置于承载网 103和业务控制层 101之间。 在业务控制层 101中的呼叫代理（CA, Call Agent )为业务服务器， 比如软 交换等， 可卖现软交换等功能； 在承载控制层 102 中， 包括一个或多个承 载网资源管理器， 承载网资源管理器负责配置管理规则和网络拓朴， 为客 户的业务带宽申请分配资源， 控制和管理各个承载网资源管理器之间通过 信令传递客户的业务带宽申请请求和结果、 以及为业务申请分配的路由路 径信息等， 比如： 控制和管理承载网资源管理器 1、 承载网资源管理器 2、 承载网资源管理器 3之间的通信； 在承载网 103 中， 每个承载网资源管理 器管理一个特定的承载网区域， 这个特定的承载网区域被称为所对应的承 载网资源管理器的管理域， 比如： 承载网资源管理器 1的管理域 105、 承载 网资源管理器 2的管理域 106和承载网资源管理器 3的管理域 107,承载网 103中包括边缘路由器（ ER， Edge Router )、边界路由器（ BR, Border Router ) 以及核心路由器 104， ER、 BR和核心路由器都属于承载网， 统称为连接节 点 ( CN, Connection Node )。 Since the Diff-serv model only guarantees QoS by setting priorities, the effect is difficult to predict. Therefore, the industry has introduced an independent bearer control layer for the Diff-Serv model of the backbone network, established a dedicated Diff-Serv QoS signaling mechanism, and used the new bearer control layer of the Diff-Serv network to manage the topology resources of the network. This Diff-Serv is called a Diff-Serv model with an independent bearer control layer. Figure 1 shows a Diff-serv model with an independent bearer control layer. As shown in FIG. 1, in the model, the bearer control layer 102 is disposed between the bearer network 103 and the service control layer 101. The call agent (CA, Call Agent) in the service control layer 101 is a service server, such as a soft switch, and the like, and can be sold as a soft switch. In the bearer control layer 102, one or more bearers are included. The network resource manager, the bearer network resource manager is responsible for configuring the management rules and the network topology, and allocating resources for the customer's service bandwidth request, and controlling and managing the service bandwidth request requests of the respective bearer network resource managers through signaling. And the result, and the routing path information allocated for the service request, for example: controlling and managing the communication between the bearer network resource manager 1, the bearer network resource manager 2, and the bearer network resource manager 3; in the bearer network 103, Each bearer network resource manager manages a specific bearer network area. This specific bearer network area is called the management domain of the corresponding bearer network resource manager, for example: the management domain 105 of the bearer network resource manager 1, and the bearer. The management domain 106 of the network resource manager 2 and the management domain 107 of the bearer network resource manager 3, the bearer network 103 includes an edge router (ER, Edge Router), a border router (BR), and a core router 104, ER, Both the BR and the core router belong to the bearer network and are collectively referred to as the connection node (CN).
在具有独立承载控制层的 Diff-Serv模型中， 承载网资源管理器配置了 管理规则和网络拓朴， 为客户的业务带宽申请分配资源。 当承载控制层处 理用户的业务带宽申请时， 承载网资源管理器将确定用户业务的路径， 并 通知边缘路由器按指定的路径转发业务流。 承载网如何根据承载控制层确 定的路径实现用户业务流按指定路由转发， 目前业界主要是利用 MPLS技 术， 使用资源预留方式沿着承载控制层指定的业务流路径建立 LSP， 使用 RSVP-TE或 CR-LDP的显示路由机制建立端到端的 LSP。  In the Diff-Serv model with independent bearer control layer, the bearer network resource manager is configured with management rules and network topology to allocate resources for the customer's service bandwidth request. When the bearer control layer processes the service bandwidth request of the user, the bearer network resource manager determines the path of the user service and notifies the edge router to forward the service flow according to the specified path. The bearer network implements the user service flow forwarding according to the specified route according to the path determined by the bearer control layer. Currently, the industry mainly uses the MPLS technology to establish an LSP along the service flow path specified by the bearer control layer by using the resource reservation mode, using RSVP-TE or The CR-LDP display routing mechanism establishes an end-to-end LSP.
现有技术中， 实现业务连接资源分配的具体处理流程如图 2 所示， 包 括以下步驟：  In the prior art, the specific processing flow for realizing the service connection resource allocation is as shown in FIG. 2, which includes the following steps:
步骤 201 :主叫 CA向与其连接的承载网资源管理器发送连接资源请求。 这里， 将与主叫 CA连接的承载网资源管理器称为源承载网资源管理器。  Step 201: The calling CA sends a connection resource request to the bearer network resource manager connected thereto. Here, the bearer network resource manager connected to the calling CA is referred to as a source bearer network resource manager.
步骤 202〜204：收到连接资源请求的承载网资源管理器判断自身是否为 当前业务连接的目的承载网资源管理器， 如果不是， 该承载网资源管理器 根据连接资源请求中的地址信息确定本域的入口路由器和出口路由器， 并 利用选路算法进行域内和域间选路， 记录相应路径资源信息， 同时， 该承 载网资源管理器向下游承载网资源管理器转发连接资源请求， 返回步骤Steps 202 to 204: The bearer network resource manager that receives the connection resource request determines whether it is the destination bearer network resource manager of the current service connection. If not, the bearer network resource manager determines the local information according to the address information in the connection resource request. Domain ingress router and egress router, and The routing algorithm is used to perform intra-domain and inter-domain routing, and the corresponding path resource information is recorded. At the same time, the bearer network resource manager forwards the connection resource request to the downstream bearer network resource manager, and returns to the step.
202; 否则， 执行步骤 205。 202; Otherwise, go to step 205.
这里，承载网资源管理器是根据自身保存的 ER接入信息以及连接资源 请求中主叫 UE的标识信息进行判断的， 该 UE标识信息可以为 IP地址， 也可以为域名信息， IP地址携带于连接资源请求的五元组中。  Here, the bearer network resource manager is determined according to the ER access information saved by the ER access information and the identity information of the calling UE in the connection resource request, and the UE identity information may be an IP address or a domain name information, and the IP address is carried in the IP address. The five-tuple of the connection resource request.
承载网资源管理器可以通过自身所辖承载网的 LSP信息和各个 CN的 路由信息确定下游承载网资源管理器， 还可以通过这两个信息及信令路由 算法来确定下游承载网资源管理器。  The bearer network resource manager can determine the downstream bearer network resource manager by using the LSP information of the bearer network and the routing information of each CN, and can also determine the downstream bearer network resource manager by using the two information and signaling routing algorithms.
步骤 205: 目的承载网资源管理器完成自身业务路由和 LSP资源分配， 并向本域内所选择路由路径对应的路由器下发 QoS策略， 然后， 向上一跳 承载网资源管理器返回连接资源响应。  Step 205: The destination bearer network resource manager completes the service routing and the LSP resource allocation, and delivers the QoS policy to the router corresponding to the selected routing path in the domain, and then returns the connection resource response to the up-hop bearer network resource manager.
步骤 206~208：收到连接资源响应的承载网资源管理器完成自身业务路 由和 LSP资源分配， 并向本域内所选择路由路径对应的路由器下发 QoS策 略， 然后， 判断自身是否为源承载网资源管理器， 如果是， 则结束处理流 程， 否则， 向自身的上一跳承载网资源管理器返回连接资源响应， 然后， 返回步骤 206。  Steps 206 to 208: The bearer network resource manager that receives the connection resource response completes its own service routing and LSP resource allocation, and delivers a QoS policy to the router corresponding to the selected routing path in the domain, and then determines whether it is the source bearer network. The resource manager, if yes, ends the processing flow, otherwise, returns a connection resource response to its own previous hop bearer network resource manager, and then returns to step 206.
从上述处理过程可以看出， 现有资源分配流程中， 承载网资源管理器 确定路由路径、 分配相应资源后， 都要将确定的 QoS策略下发给承载网中 的路由设备， 但是， 这就需要在承载控制层和承载网设备之间建立许多通 信信道， 用于承载网资源管理器与路由设备之间的交互， 如此， 不仅会加 大承载网***的资源开销， 增加承载网的运行负荷， 而且增大了整个*** 处理的复杂度。  It can be seen from the above process that in the existing resource allocation process, after the bearer network resource manager determines the routing path and allocates the corresponding resource, the determined QoS policy is sent to the routing device in the bearer network, but this A plurality of communication channels are required to be established between the bearer control layer and the bearer network device for carrying the interaction between the network resource manager and the routing device. Therefore, not only the resource overhead of the bearer network system but also the operational load of the bearer network is increased. And increase the complexity of the entire system processing.
另外， 承载控制层和承载网是两个相互独立的层面， 每层中的网络设 备也是相互独立的， 因此， 如果承载控制层所采用的网络设备与承载网设 备不属于同一厂家， 那么， 还存在两个厂家网络设备之间功能相互支持的 问题， 如果有些功能如保证 QoS功能相互不能支持， 但又要求两层设备之 间完成此功能时必须交互， 这样就有可能导致整个***中业务连接的 QoS 不能得到保障。 发明内容 In addition, the bearer control layer and the bearer network are two independent layers, and the network devices in each layer are also independent of each other. Therefore, if the network device and the bearer network used by the bearer control layer are used, If the device does not belong to the same manufacturer, there are still problems in the mutual support between the two network devices. If some functions, such as ensuring that QoS functions cannot support each other, but require two layers of devices to perform this function, they must interact. It is possible that the QoS of the service connection in the entire system cannot be guaranteed. Summary of the invention
有鉴于此， 本发明的主要目的在于提供一种实现业务连接资源管理的 方法， 能减轻***资源开销和运行负荷， 并且能保证整个***每个业务流 的 QoS。  In view of this, the main object of the present invention is to provide a method for implementing service connection resource management, which can reduce system resource overhead and operation load, and can ensure QoS of each service flow of the entire system.
为达到上述目的， 本发明的技术方案是这样实现的：  In order to achieve the above object, the technical solution of the present invention is achieved as follows:
一种实现业务连接资源管理的方法， 该方法包括以下步骤：  A method for implementing service connection resource management, the method comprising the following steps:
a. 呼叫代理收到主叫用户的业务连接请求后， 向源承载网资源管理器 发送连接资源请求；  a. After receiving the service connection request of the calling user, the call proxy sends a connection resource request to the source bearer network resource manager;
b. 收到连接资源请求的承载网资源管理器进行域内和域间选路， 申请 并记录域内和域间路径资源， 并判断自身是否为目的承载网资源管理器， 如果是， 则执行步骤 c; 否则， 当前承载网资源管理器向下一跳承载网资源 管理器转发连接资源请求， 返回步骤 b;  b. The bearer network resource manager that receives the connection resource request performs intra-domain and inter-domain routing, applies for and records the intra-domain and inter-domain path resources, and determines whether it is the destination bearer network resource manager. If yes, step c is performed. Otherwise, the current bearer network resource manager forwards the connection resource request to the next hop bearer network resource manager, and returns to step b;
c. 完成业务路由、 路径资源分配， 之后不向承载网路由设备下发 QoS 策略， 立即向上一跳承载网资源管理器返回连接资源响应， 直到将连接资 源响应发至源承载网资源管理器。  After the service routing and the path resource allocation are completed, the QoS policy is not sent to the bearer network routing device, and the connection resource response is immediately returned to the bearer network resource manager until the connection resource response is sent to the source bearer network resource manager.
其中， 步骤 b进一步包括： 每个承载网资源管理器才队据连接资源请求 中的地址信息确定本域内的入口路由器， 再根据所确定的入口路由器利用 路由算法进行域内和域间的选路， 并确定本域内的出口路由器。 所述连接 资源响应中携带有当前承载网资源管理器的路径资源和当前承载网资源管 理器下一跳承载网资源管理器返回的路径资源。  Step b further includes: each bearer network resource manager determines the ingress router in the domain according to the address information in the connection resource request, and then uses the routing algorithm to perform intra-domain and inter-domain routing according to the determined ingress router. And determine the egress router in this domain. The connection resource response carries the path resource of the current bearer network resource manager and the path resource returned by the current bearer network resource manager next hop bearer network resource manager.
上述方案中， 每个承载网资源管理器中保存有自身所管理的承载网的 拓朴和全部资源信息。 所述承载网的拓朴和资源信息根据网络的实际情况 通过配置得到； 或者， 通过基于流量工程的路由协议或 SNMP协议动态收 集得到， 或者， 通过对 COPS标准协议扩展得到。 承载网的拓朴和资源信 息发生变化时， 该方法进一步包括： 将对应的承载网资源管理器上的数据 信息进行同步。 In the foregoing solution, each bearer network resource manager stores a bearer network managed by itself. Topology and full resource information. The topology and resource information of the bearer network are obtained through configuration according to the actual situation of the network; or dynamically collected through a traffic engineering-based routing protocol or an SNMP protocol, or obtained by extending the COPS standard protocol. When the topology of the bearer network and the resource information are changed, the method further includes: synchronizing the data information on the corresponding bearer network resource manager.
上述方案中， 所述承载网为 IP网络、 或 MPLS网络、 或 ATM网络。 相应的， 所述路径资源为标签交换路径、 或隧道、 或永久虚电路、 或交换 式虛电路。 所述连接资源请求为业务申请请求、 或业务修改请求、 或业务 释放请求。  In the foregoing solution, the bearer network is an IP network, or an MPLS network, or an ATM network. Correspondingly, the path resource is a label switched path, or a tunnel, or a permanent virtual circuit, or an switched virtual circuit. The connection resource request is a service request request, or a service modification request, or a service release request.
本发明所提供的实现业务连接资源管理的方法， 去掉了承载网资源管 理器向承载网设备发送 QoS策略的步骤， 目的承载网资源管理器完成业务 路由和路径资源分配后， 直接向上一跳承载网资源管理器返回响应， 源承 向上一跳返回响应， 直到源承载网资源管理器。 如此， 就不需要在承载控 制层和承载网路由设备之间为下传 QoS策略等信息而建立通信信道， 从而 减轻了承载网***的资源开销， 降低了承载网的运行负荷， 而且减小了整 个***处理的复杂度。  The method for implementing the service connection resource management provided by the present invention removes the step of the bearer network resource manager transmitting the QoS policy to the bearer network device, and the destination bearer network resource manager directly performs the uplink hop after the service route and the path resource allocation are completed. The network resource manager returns a response, and the source inherits the response from the previous hop until the source hosts the network resource manager. In this way, it is not necessary to establish a communication channel between the bearer control layer and the bearer network routing device for downlink QoS policy and the like, thereby reducing the resource overhead of the bearer network system, reducing the running load of the bearer network, and reducing the operation load. The complexity of the entire system processing.
同时， 由于承载控制层不需要与承载网路由设备相互配合， 因此， 即 使两个层面采用不同厂家的设备也不会影响业务连接的 QoS, 能充分保障 整个***的 QoS, 解决了 Differ-serv模型中不能为每个业务流提供 QoS保 证的问题， 便于各种规模的网络进行商用。  At the same time, since the bearer control layer does not need to cooperate with the routing device of the bearer network, even if devices of different vendors are used at two levels, the QoS of the service connection will not be affected, and the QoS of the entire system can be fully guaranteed, and the Differ-serv model is solved. It is not possible to provide QoS guarantee for each service flow, which is convenient for commercial networks of various sizes.
另夕卜，本发明的方法可用于各种承载网，如包含 MPLS网络的 IP网络、 ATM网络和其它类型的承载网， 相应的， 对应的路径可以是 LSP、 tunnel PVC、 SVC 等等， 因此， 本发明的适用范围更广、 实用性更强， 使用更灵 活。 由于现有承载网设备已支持动态路由协议、 SNMP协议等等， 故此， 本发明对承载网改动很小， 易于实现。 附图简要说明 In addition, the method of the present invention can be applied to various bearer networks, such as an IP network including an MPLS network, an ATM network, and other types of bearer networks. Correspondingly, the corresponding path may be LSP, tunnel PVC, SVC, etc., The invention has wider application range, more practicality and more flexible use. Since the existing bearer network device already supports the dynamic routing protocol, the SNMP protocol, and the like, the present invention has little change to the bearer network and is easy to implement. BRIEF DESCRIPTION OF THE DRAWINGS
图 1为现有技术中独立的承载控制层网络模型示意图；  1 is a schematic diagram of a network model of an independent bearer control layer in the prior art;
图 2为现有技术中实现资源分配的处理流程图；  2 is a flowchart of processing for realizing resource allocation in the prior art;
图 3为本发明实现业务连接资源管理的处理流程图。 实施本发明的方式  FIG. 3 is a flowchart of processing for implementing service connection resource management according to the present invention. Mode for carrying out the invention
本发明的核心思想是： 源承载网资源管理器收到业务控制层发来的资 源请求后， 完成自身的业务路由和路径资源分配， 并向下一跳转发连接资 源请求， 直至目的承载网资源管理器， 每个接收到连接资源请求的承载网 资源管理器均完成自身的业务路由和路径资源分配； 目的承载网资源管理 器完成业务路由和路径资源分配后， 立即向上一跳承载网资源管理器返回 连接资源响应， 直至源承载网资源管理器， 而无须向承载网设备发送 QoS 策略。 其中， 连接资源响应中携带有自身和自身下一跳承载网资源管理器 的路径资源信息。  The core idea of the present invention is: After receiving the resource request sent by the service control layer, the source bearer network resource manager completes its own service route and path resource allocation, and forwards the connection resource request to the next hop until the destination bearer network The resource manager, each bearer network resource manager that receives the connection resource request completes its own service route and path resource allocation; after the destination bearer network resource manager completes the service route and the path resource assignment, immediately forwards the network resource to the next hop. The manager returns a connection resource response until the source hosts the network resource manager without sending a QoS policy to the bearer network device. The connection resource response carries path resource information of the own and its next hop bearer network resource manager.
本发明中， 每个承载网资源管理器中保存有自身所管理的承载网的拓 朴信息和全部资源信息， 所保存信息的取得途径可以是根据网络的实际应 用情况通过手工配置的； 也可以是通过基于流量工程的现有路由协议或 SNMP协议进行收集的， 或是对 COPS等标准协议进行扩展完成的。  In the present invention, each bearer network resource manager stores topology information and all resource information of the bearer network managed by itself, and the path for obtaining the saved information may be manually configured according to actual application conditions of the network; It is collected through existing routing protocols based on traffic engineering or SNMP protocol, or extended by standard protocols such as COPS.
当承载网的拓朴结构或资源信息.发生变化时， 与发生变化的承载网对 应的承载网资源管理器中的数据信息要进行同步更新； 如果已经承载业务 连接， 则进行相应的故障处理， 可以直接拆除连接或通知业务控制层的呼 叫代理， 由呼叫代理来决定如何处理。  When the topology of the bearer network or the resource information changes, the data information in the bearer network resource manager corresponding to the changed bearer network is updated synchronously; if the service connection is already carried, the corresponding fault processing is performed. The call agent that connects or notifies the service control layer can be directly removed, and the call agent decides what to do.
当业务呼叫代理在建立业务连接时， 需要向承载网资源管理器发送查 询资源请求， 比如： 查询带宽参数、 其它 QoS参数等等， 承载网资源管理 器根据自身掌握的网络具体拓朴情况和业务连接的 QoS要求， 进行选路和 资源计算， 向业务呼叫代理响应结果， 如果满足所规定的 QoS策略要求， 则可以建立本次业务连接， 否则不可以建立本次业务连接。 When the service call agent establishes a service connection, it needs to send a check to the bearer network resource manager. Request resource requests, such as: query bandwidth parameters, other QoS parameters, etc. The bearer network resource manager performs routing and resource calculation according to the specific topology of the network and the QoS requirements of the service connection, and responds to the service call agent. If the required QoS policy is met, the service connection can be established. Otherwise, the service connection cannot be established.
如果业务连接的源端和目的端在同一个承载网资源管理器的管辖范围 内， 则该承载网资源管理器 居资源计算结果就可以向业务控制层返回响 应； 否则， 需要发送资源请求到其它承载网资源管理器上， 每个承载网资 源管理器进行相应的拓朴和资源计算， 最后将结果返回给发起业务连接资 源请求的呼叫代理。  If the source end and the destination end of the service connection are within the jurisdiction of the same bearer network resource manager, the bearer network resource manager may return a response to the service control layer; otherwise, the resource request needs to be sent to the other On the bearer network resource manager, each bearer network resource manager performs corresponding topology and resource calculation, and finally returns the result to the call agent that initiates the service connection resource request.
对于业务连接的资源修改和资源释放， 上述过程同样适用。  The same applies to resource modification and resource release for business connections.
本发明中所述的承载网可以是包含 MPLS网络在内的 IP网络、 ATM网 络或其它类型的承载网， 因此， 对应的路径可以是标签交换路径（LSP )、 隧道（tunnel )、 永久虚电路（ PVC )、 交换式虚电路（ SVC )等。  The bearer network in the present invention may be an IP network including an MPLS network, an ATM network, or another type of bearer network. Therefore, the corresponding path may be a label switched path (LSP), a tunnel, or a permanent virtual circuit. (PVC), switched virtual circuit (SVC), etc.
本发明中所述连接资源请求可以是业务申请请求、 或业务修改请求、 或业务释放请求。  The connection resource request in the present invention may be a service application request, or a service modification request, or a service release request.
如图 3所示， 本发明的具体处理流程包括以下步骤：  As shown in FIG. 3, the specific processing procedure of the present invention includes the following steps:
步骤 301 : 呼叫代理收到主叫用户的业务连接请求后， 向与其连接的承 载网资源管理器发送连接资源请求； 承载网资源管理器为当前业务流保存 连接信息。 这里， 与呼叫代理连接的承载网资源管理器称为源承载网资源 管理器， 被叫用户所属的承载网资源管理器称为目的承载网资源管理器， 源承载网资源管理器与目的承载网资源管理器之间的承载网资源管理器称 为中间承载网资源管理器。  Step 301: After receiving the service connection request of the calling user, the call agent sends a connection resource request to the bearer network resource manager connected thereto; the bearer network resource manager saves the connection information for the current service flow. Here, the bearer network resource manager connected to the call agent is called the source bearer network resource manager, and the bearer network resource manager to which the called user belongs is called the destination bearer network resource manager, the source bearer network resource manager and the destination bearer network. The bearer network resource manager between resource managers is called an intermediate bearer network resource manager.
步骤 302:收到连接资源请求的承载网资源管理器根据连接资源请求中 五元组的源 IP地址， 确定自身管理域的入口路由器。  Step 302: The bearer network resource manager that receives the connection resource request determines the ingress router of the own management domain according to the source IP address of the quintuple in the connection resource request.
对于源承载网资源管理器， 就是根据连接资源请求中五元组的源 IP地 址， 确定该源 IP地址归属于哪个 ER。 For the source bearer network resource manager, it is based on the source IP address of the quintuple in the connection resource request. The address determines which ER the source IP address belongs to.
对于其它中间承载网资源管理器， 则是根据连接资源请求中携带的 IP 地址确定本域的入口 BR， 例如： 逐跳路由算法就是由上一跳承载网资源管 理器选择好域间路径， 根据该路径即可确定本域的入口路由器和上一跳承 载网资源管理器管理域的出口路由器。  For other intermediate bearer network resource managers, the ingress BR of the local domain is determined according to the IP address carried in the connection resource request. For example, the hop-by-hop routing algorithm selects the inter-domain path by the previous hop bearer network resource manager, according to The path can determine the ingress router of the domain and the egress router of the management domain of the previous hop bearer network resource manager.
步骤 303： 当前承载网资源管理器利用业务路由算法在自身的管理域内 进行域内选路， 申请域内路径资源， 并记录这些路径资源信息。 这里， 可 以采用任意已有的域内选路算法来实现域内选路， 比如： 采用 Dijakstra算 法、 Bdlman-Ford算法、 静态配置算法、 或矩阵路由表的方法。  Step 303: The current bearer network resource manager uses the service routing algorithm to perform intra-domain routing in its own management domain, apply for intra-domain path resources, and record the path resource information. Here, any existing intra-domain routing algorithm can be used to implement intra-domain routing, such as: Dijakstra algorithm, Bdlman-Ford algorithm, static configuration algorithm, or matrix routing table method.
步骤 304: 当前承载网资源管理器利用信令路由算法在自身与下一跳承 载网资源管理器之间进行域间选路， 确定本域内的出口路由器。 这里， 可 以釆用任意已有的域间选路算法来实现域间选路， 比如： 逐跳路由、 正向 约束反向路由等等。  Step 304: The current bearer network resource manager uses the signaling routing algorithm to perform inter-domain routing between itself and the next hop carrier network resource manager to determine an egress router in the domain. Here, any existing inter-domain routing algorithm can be used to implement inter-domain routing, such as hop-by-hop routing, forward-constrained reverse routing, and so on.
步骤 305〜306：当前承载网资源管理器判断自身是否为目的承载网资源 管理器， 如果是， 则执行步骤 307; 否则， 当前承载网资源管理器向下一跳 承载网资源管理器转发连接资源请求， 返回步骤 302。  Steps 305-306: The current bearer network resource manager determines whether it is the destination bearer network resource manager. If yes, step 307 is performed; otherwise, the current bearer network resource manager forwards the connection resource to the next-hop bearer network resource manager. The request returns to step 302.
步骤 307: 目的承载网资源管理器完成业务路由、 路径资源分配， 之后 向上一跳承载网资源管理器返回连接资源响应。 这里， 承载网资源管理器 不向承载网的路由设备下发 QoS策略。  Step 307: The destination bearer network resource manager completes service routing and path resource allocation, and then returns a connection resource response to the uplink hop bearer network resource manager. Here, the bearer network resource manager does not deliver the QoS policy to the routing device of the bearer network.
步骤 308: 收到连接资源响应的承载网资源管理器， 向上一跳承载网资 源管理器返回连接资源响应， 重复本步骤直至源承载网资源管理器。  Step 308: The bearer network resource manager that receives the connection resource response returns the connection resource response to the up-hop bearer network resource manager, and repeats this step until the source bearer network resource manager.
其中， 所述连接资源响应中携带有自身的路径资源信息和; F—跳承载 网资源管理器返回的路径资源信息。  The connection resource response carries its own path resource information and the F-hop resource information returned by the bearer network resource manager.
步骤 309:源承载网资源管理器将选路和路径资源信息返回给发起请求 的呼叫代理。 本发明无需承载控制层的承载网资源管理器向承载网的路由设备下发Step 309: The source bearer network resource manager returns the routing and path resource information to the calling proxy that initiated the request. The present invention does not need to carry the bearer network resource manager of the control layer to deliver the routing device to the bearer network.
QoS 策略， 而是通过配置和动态收集承载网拓朴结构信息和资源信息， 生 成用于业务连接资源动态分配的映射信息 （mapping ), 并通过流量工程方 式进行路由选路和资源计算， 进而保证业务连接在承载网中的 QoS。 这里， 如何根据拓朴信息和资源信息生成映射信息， 以及如何通过流量工程方式 进行路由选路和资源计算保证 QoS, 属于现有技术， 在实际应用中对具体 的实现方法不作限定。 比如说： 某个承载网资源管理器可以通过 SNMP等 协议从承载网中收集拓朴信息和资源信息， 之后， 该承载网资源管理器将 收集到的信息放入自身的数据库中； 等到上游业务连接请求过来时， 该承 载网资源管理器根据提前配置好的流量工程策略， 如根据时延最小原则或 成本最小原则等策略进行选路， 并进行带宽等资源的计算； 最后， 该承载 网资源管理器向自身下游承载网资源管理器继续申请、 或向自身上游承载 网资源管理器反馈结果。 如此， 就可以保证业务连接在承载网中的 QoS。 The QoS policy is configured to dynamically collect the mapping structure information and resource information of the bearer network, generate mapping information for dynamic allocation of service connection resources, and perform routing and resource calculation through traffic engineering, thereby ensuring The QoS of the service connection in the bearer network. Here, how to generate mapping information according to the topology information and the resource information, and how to ensure the QoS by using the traffic engineering method for route routing and resource calculation is a prior art, and the specific implementation method is not limited in practical applications. For example: a bearer network resource manager can collect topology information and resource information from a bearer network through a protocol such as SNMP. After that, the bearer network resource manager puts the collected information into its own database; When the connection request comes over, the bearer network resource manager performs routing according to a traffic management policy configured in advance, such as a minimum delay principle or a minimum cost principle, and performs calculation of bandwidth and other resources. Finally, the bearer network resource The manager continues to apply to its own downstream bearer network resource manager or feeds back the results to its own upstream bearer network resource manager. In this way, the QoS of the service connection in the bearer network can be guaranteed.
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。  The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

权利要求书 Claim
1、 一种实现业务连接资源管理的方法， 其特征在于， 该方法包括以下 步骤：  A method for implementing service connection resource management, characterized in that the method comprises the following steps:
a. 呼叫代理收到主叫用户的业务连接请求后， 向源承载网资源管理器 发送连接资源请求；  a. After receiving the service connection request of the calling user, the call proxy sends a connection resource request to the source bearer network resource manager;
b. 收到连接资源请求的承载网资源管理器进行域内和域间选路， 申请 并记录域内和域间路径资源， 并判断自身是否为目的承载网资源管理器， 如果是， 则执行步骤 c; 否则， 当前承载网资源管理器向下一跳承载网资源 管理器转发连接资源请求， 返回步骤 b;  b. The bearer network resource manager that receives the connection resource request performs intra-domain and inter-domain routing, applies for and records the intra-domain and inter-domain path resources, and determines whether it is the destination bearer network resource manager. If yes, step c is performed. Otherwise, the current bearer network resource manager forwards the connection resource request to the next hop bearer network resource manager, and returns to step b;
c. 完成业务路由、 路径资源分配， 之后不向承载网路由设备下发 QoS 策略， 直接向上一跳承载网资源管理器返回连接资源响应， 直到将连接资 源响应发至源承载网资源管理器。  After the service routing and the path resource allocation are completed, the QoS policy is not sent to the bearer network routing device, and the connection resource response is directly returned to the bearer network resource manager until the connection resource response is sent to the source bearer network resource manager.
2、 根据权利要求 1所述的方法， 其特征在于， 步骤 b进一步包括： 每 个承载网资源管理器根据连接资源请求中的地址信息确定本域内的入口路 由器， 再根据所确定的入口路由器利用路由算法进行域内和域间的选路 , 并确定本域内的出口路由器。  The method according to claim 1, wherein the step b further comprises: each bearer network resource manager determining an ingress router in the domain according to the address information in the connection resource request, and then utilizing the determined ingress router according to the determined The routing algorithm performs routing within and between domains and determines the egress routers within the domain.
3、 根据权利要求 1所述的方法， 其特征在于， 所述连接资源响应中携 带有当前承载网资源管理器的路径资源和当前承载网资源管理器下一跳承 载网资源管理器返回的路径资源。  The method according to claim 1, wherein the connection resource response carries the path resource of the current bearer network resource manager and the path returned by the current bearer network resource manager next hop bearer network resource manager. Resources.
4、 根据权利要求 1所述的方法， 其特征在于， 每个承载网资源管理器 中保存有自身所管理的承载网的拓朴和全部资源信息。  4. The method according to claim 1, wherein each bearer network resource manager stores topology and all resource information of the bearer network managed by itself.
5、 根据权利要求 4所述的方法， 其特征在于， 所述承载网的拓朴和资 源信息根据网络的实际情况通过配置得到； 或者， 通过基于流量工程的路 由协议或 SNMP协议动态收集得到， 或者， 通过对 COPS标准协议扩展得 到。 The method according to claim 4, wherein the topology and resource information of the bearer network are obtained through configuration according to actual conditions of the network; or dynamically collected by using a traffic engineering-based routing protocol or an SNMP protocol, Or, by extending the COPS standard protocol.
6、 根据权利要求 4所述的方法， 其特征在于， 所述承载网的拓朴和资 源信息发生变化时， 该方法进一步包括： 将对应的承载 ^资源管理器上的 数据信息进行同步。 The method according to claim 4, wherein, when the topology and resource information of the bearer network are changed, the method further comprises: synchronizing data information on the corresponding bearer resource manager.
7、 根据权利要求 1至 6任一项所述的方法， 其特征在于， 所述承载网 为 IP网络、 或 MPLS网络、 或 ATM网络。  The method according to any one of claims 1 to 6, wherein the bearer network is an IP network, or an MPLS network, or an ATM network.
8、 根据权利要求 7所述的方法， 其特征在于， 所述路径资源为标签交 换路径、 或隧道、 或永久虚电路、 或交换式虚电路。  8. The method according to claim 7, wherein the path resource is a label switching path, or a tunnel, or a permanent virtual circuit, or a switched virtual circuit.
9、 根据权利要求 1至 6任一项所述的方法， 其特征在于， 所述连接资 源请求为业务申请请求、 或业务修改请求、 或业务释放请求。  The method according to any one of claims 1 to 6, wherein the connection resource request is a service request request, or a service modification request, or a service release request.
u u
PCT/CN2005/001714 2004-10-20 2005-10-19 A method for achieving the service connection resource management WO2006042464A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200410086418.5 2004-10-20
CNB2004100864185A CN100382540C (en) 2004-10-20 2004-10-20 Method for realizing service connection resource management

Publications (1)

Publication Number Publication Date
WO2006042464A1 true WO2006042464A1 (en) 2006-04-27

Family

ID=36202675

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/001714 WO2006042464A1 (en) 2004-10-20 2005-10-19 A method for achieving the service connection resource management

Country Status (2)

Country Link
CN (1) CN100382540C (en)
WO (1) WO2006042464A1 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101132325B (en) * 2006-08-21 2010-10-13 华为技术有限公司 Business applying method and system and business application proxy unit
KR101058605B1 (en) * 2006-09-28 2011-08-22 콸콤 인코포레이티드 Bundling of Communication Signals for Efficiency
JP5059555B2 (en) * 2007-11-07 2012-10-24 株式会社エヌ・ティ・ティ・ドコモ Mobile communication system, radio network controller, mobile station, exchange, and radio network control method

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1425256A (en) * 1999-12-31 2003-06-18 诺基亚公司 Packet routing in multi-bearer-type network
US20030169726A1 (en) * 2000-06-27 2003-09-11 Larsson Gunnar Bengt Connectionless routing of data within a telecommunication gateway
CN1523834A (en) * 2003-02-20 2004-08-25 ��Ϊ�������޹�˾ IP network service quality assurance method and system

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20040001235A (en) * 2002-06-27 2004-01-07 주식회사 케이티 Method for proviging network service by class on Asynchronous Transfer Mode network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1425256A (en) * 1999-12-31 2003-06-18 诺基亚公司 Packet routing in multi-bearer-type network
US20030169726A1 (en) * 2000-06-27 2003-09-11 Larsson Gunnar Bengt Connectionless routing of data within a telecommunication gateway
CN1523834A (en) * 2003-02-20 2004-08-25 ��Ϊ�������޹�˾ IP network service quality assurance method and system

Also Published As

Publication number Publication date
CN1764151A (en) 2006-04-26
CN100382540C (en) 2008-04-16

Similar Documents

Publication Publication Date Title
JP3492950B2 (en) Method for providing quality of service for delay-sensitive traffic transmitted over an internet network
KR100822707B1 (en) Apparatus and method for managing quality of service in integrated network of heterogeneous mobile networks
US7184434B2 (en) Label distribution protocol supporting multiple classes of service in a multi protocol label switching (MPLS) network, methods and MPLS network using thereof
EP1589696B1 (en) System and method for resource allocation in a multi-domain network
US7652987B2 (en) Method and system for guaranteeing reliability of end-to-end quality of service
AU754325B2 (en) Method and apparatus for providing guaranteed quality/class of service within and across networks using existing reservation protocols and frame formats
US7561586B2 (en) Method and apparatus for providing network VPN services on demand
US7327681B2 (en) Admission control method in internet differentiated service network
EP1838039B1 (en) An implementing method of multiple service flows resource application
US20070147243A1 (en) Method and system for guaranteeing end-to-end quality of service
US20040082338A1 (en) Network resource manager in a mobile telecommunication system
JP2006508605A (en) Hierarchical resource management configuration and method in a hierarchical network architecture
JP2005502275A (en) Method and apparatus in IP communication network
US7633958B2 (en) Method of resource reservation across a plurality of domains
WO2006056099A1 (en) A method and system for delaminatly ensuring the network service quality
EP1821455B1 (en) A method for forwarding the traffic flow in the bearer network
WO2006042464A1 (en) A method for achieving the service connection resource management
JP3923908B2 (en) Communication quality management system and method
Lin et al. A QoS model of Next Generation Network based on MPLS
CN100391154C (en) Selecting method of path in resource supervisor
KR100794363B1 (en) Web Service based Inter-Domain Connection Managements for QoS-guaranteed Inter-networking
Chen et al. Using policy-based MPLS management architecture to improve QoS on IP network
Kim et al. Controlled Bandwidth Borrowing with Extended RSVP-TE to Maximize Bandwidth Utilization
Shi A proposal for RSVP over differentiated services networks

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV LY MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 05806187

Country of ref document: EP

Kind code of ref document: A1