WO2005013553A1 - Procede permettant de fournir une qualite de service fiable dans un reseau de communication - Google Patents

Procede permettant de fournir une qualite de service fiable dans un reseau de communication Download PDF

Info

Publication number
WO2005013553A1
WO2005013553A1 PCT/CN2004/000870 CN2004000870W WO2005013553A1 WO 2005013553 A1 WO2005013553 A1 WO 2005013553A1 CN 2004000870 W CN2004000870 W CN 2004000870W WO 2005013553 A1 WO2005013553 A1 WO 2005013553A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer network
network resource
resource manager
service
quality
Prior art date
Application number
PCT/CN2004/000870
Other languages
English (en)
French (fr)
Inventor
Yuepeng Chen
Lingyuan Fan
Ting Zou
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.
Priority to DE602004027499T priority Critical patent/DE602004027499D1/de
Priority to AT04738444T priority patent/ATE470293T1/de
Priority to EP04738444A priority patent/EP1650895B1/en
Priority to US10/566,739 priority patent/US7746843B2/en
Publication of WO2005013553A1 publication Critical patent/WO2005013553A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
    • H04L47/762—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/15—Flow control; Congestion control in relation to multipoint traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/783—Distributed allocation of resources, e.g. bandwidth brokers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/805—QOS or priority aware
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1043—Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS

Definitions

  • the present invention relates to the field of network communication technologies, and in particular, to a method for providing reliable transmission service quality in a communication network. Background of the invention
  • an independent bearer control layer is introduced for the backbone network Diff-Serv model to manage the resources of the bearer network accordingly.
  • IETF and some manufacturers and research institutions jointly promote the quality of service backbone network (Qbone) test network, using the bearer network resource manager to implement bearer network resources and topology management, that is, management topology Resources and coordinate the QoS capabilities of each Diff-Serv model area.
  • Qbone quality of service backbone network
  • the Diff-Serv method is a Diff-Serv model with an independent bearer control layer.
  • the resource management rules of the bearer network connection nodes and the network topology are configured in the bearer network resource manager, and the bearer network resource manager is responsible for user service bandwidth requests Allocate resources.
  • Each bearer network resource manager transmits the service bandwidth request and result of the user, and the path information allocated by the bearer network resource manager to the service through signaling.
  • the bearer control layer When the bearer control layer processes a user's service bandwidth request, it will determine the user's service path, and the bearer network resource manager will notify the edge router, that is, the connecting node of the bearer network, to forward the service flow according to the specified path.
  • the Internet 2 (Internet 2) specifically defines corresponding bandwidth agents (BB), call agents (CA), or connection managers (CM) for each Diff-Serv model management domain. )
  • the bandwidth agent is responsible for processing bandwidth requests from user hosts, or service servers, or network maintenance personnel, and the bandwidth agent is based on the current network resource reservation status and configuration policy and with the user
  • the signed service level agreement (SLA) determines whether the user's bandwidth request is allowed; the call agent is used as a service server, that is, used to connect a user's call to a communication network; the connection management is described
  • the router is used to enable the service layer to control the bearer network layer according to the service requirements.
  • the above-mentioned Diff-Serv model with independent bearer control layer based on the bandwidth agent has a problem.
  • SIBBS Simple Inter-domain Bandwidth Broker signaling
  • This signaling can only be used between bandwidth agents, and there is no resource synchronization mechanism between bandwidth agents, that is, the resource request is sent directly through the SIBBS, and there is no session establishment and maintenance process, and no Message interaction mechanism for maintenance management.
  • an object of the present invention is to provide a method for providing a reliable transmission service shield amount in a communication network, so as to ensure that the bearer network can effectively manage the entire network resources and ensure the reliability of important service transmissions in the network.
  • the present invention provides a method for providing reliable transmission service quality in a communication network.
  • the method includes the following steps:
  • the present invention is on a control layer of a bearer network
  • the QoS connection is established between the bearer network resource managers, and the established QoS connection is maintained and managed.
  • various QoS resource control messages can be carried and each bearer network resource manager at the bearer network control layer can be carried. Between them, thereby realizing the transfer of information such as service bandwidth requests and results, and path information allocated for service requests in a communication network.
  • the method for establishing a QoS connection between bearer network resource managers provided by the present invention is simple and reliable to implement, and the QoS connection is easy to maintain and has good controllability.
  • the invention also realizes the resource synchronization mechanism and operation and maintenance mechanism between the resource managers of the bearer network, and overcomes the shortcomings of the resource synchronization mechanism not implemented between the bandwidth agents in the prior art that uses SIBBS signaling to implement resource requests. .
  • the present invention also realizes the transmission of resource requests and status reports between the local bearer network resource manager and the peer bearer network resource manager, which further improves the performance of the established QoS connection. Therefore, the implementation of the present invention enables the resources of the bearer network to be conveniently and uniformly managed, and provides technical support for ensuring transmission reliability of important services in the network.
  • Figure la shows a schematic diagram of the networking structure of a communication network
  • FIG. 1b shows a networking diagram of a bearer network resource manager of a communication network
  • FIG. 2 shows a flowchart of establishing a connection in the present invention
  • FIG. 3 shows a flowchart of transmitting quality of service resource control messages in the present invention
  • FIG. 4 shows a flowchart of allocating quality of service resources in the present invention
  • FIG. 5 shows a flowchart of releasing quality of service resources in the present invention
  • FIG. 6 shows a flowchart of modifying a quality of service resource in the present invention
  • FIG. 7 shows a flowchart of querying the quality of service connection status in the present invention.
  • the present invention solves the problem that a QoS connection cannot be established between CMs or between CAs and CMs through signaling in a communication network, and that SIBBS is used to implement resource requests in the prior art, and there is no resource synchronization between bandwidth agents (BBs). Problems with the mechanism.
  • the core of the method for providing reliable transmission of the service shield amount in the communication network is as follows: in the communication network, each bearer network resource manager reliably transfers quality of service resource control messages, and each resource manager uses the service quality The resource control message provides the required amount of service shield for the corresponding business, so as to ensure that the corresponding transmission service quality can be reliably provided according to the transmission requirements of the business.
  • a QoS connection needs to be first established between resource managers of a bearer network, and the QoS connection is used to transmit monthly good service quality resource control messages.
  • the present invention also realizes the resource request and status report between the bearer network resource managers, which further improves the reliability of providing corresponding transmission service quality in the communication network.
  • the present invention implements the delivery of quality of service resource control messages between the BB, CA, and CM, and the delivery process includes complete processing such as establishing a connection and maintaining a connection. It can be considered that the present invention is implemented based on the Connection Initialization Protocol (RCIP), and a specific process for implementing the present invention based on RCIP will be described in detail through the following description.
  • RCIP Connection Initialization Protocol
  • the process of establishing a QoS connection between a bearer network resource manager (CM) in the present invention includes the following steps:
  • Step 21 When it is determined that the resources in the bearer network need to be controlled and managed by the bearer network resource manager located at the control layer of the bearer network, the local bearer network resource manager in the initial state manages the peer bearer network resource in the initial state
  • the server sends a connection establishment request. For example, it may send an "OPEN" message as a connection establishment request, requesting to establish a QoS connection between the local bearer network resource manager and the peer bearer network resource manager.
  • the information carried in the connection establishment request includes: the identification and authentication information of the bearer network resource manager that initiated the establishment of a connection request, so that the peer bearer network resource manager performs authentication on whether to establish a connection according to the authentication information.
  • connection establishment request may optionally include data consistency information, where the data consistency information is used to ensure that the message is not tampered during transmission and to prevent illegal message intrusion.
  • the data consistency message usually includes: 32 It consists of bits (KEY_ID), 32bits sequence number, and 96bits digest, where KEY_ID is used to identify the key value and algorithm shared by both parties.
  • the sequence number is initialized when the "OPEN" message is sent, and the follow-up The order of messages increases, and it restarts from 0 when it overflows to avoid illegal message intrusion.
  • the local bearer network resource manager is usually configured with management rules required for managing bearer network resources and network topology information of the bearer network, and can implement corresponding resource control management functions, such as resources that can complete corresponding bandwidth requests Allocate work, allocate corresponding path information for service requests in the network, and so on.
  • the bearer network control layer usually includes multiple bearer network resource managers, such as the local bearer network resource manager, multiple intermediate bearer network resource managers, and peer bearer network resource management in Figure lb.
  • the local end, the middle end, and the peer end are all for a specific QoS connection.
  • the starting point of a QoS connection is called the local bearer network resource manager, and the end point is called the peer bearer network resource manager.
  • Each bearer network resource manager that a message transmitted between the local bearer network resource manager and the peer bearer network resource manager passes through is referred to as an intermediate bearer network resource manager.
  • the local bearer network resource manager In a communication network, the local bearer network resource manager usually needs to pass multiple intermediate bearer network resource managers to finally send corresponding messages to the peer bearer network resource manager, that is, usually a quality of service resource control message needs to pass through Starting from the local bearer network resource manager, and through the process of multiple intermediate bearer network resource managers, the peer bearer network resource manager can be reached. Finally, the peer bearer network resource manager implements the resources on the corresponding connected nodes. For control management, the connection node is usually a router.
  • Step 22 After receiving the "OPEN" message from the peer bearer network resource manager, the peer bearer network resource manager determines to issue a connection establishment request based on the received authentication information and its identity. Validity of the identity of the local bearer network resource manager, if the identity of the local bearer network resource manager is valid, the peer bearer network resource manager sends a connection establishment response to the local bearer network resource manager, and the connection establishment response It carries relevant information for establishing a QoS connection. For example, the peer bearer network resource manager can send an "ACCEPT" message to the local bearer network resource manager as a response to establish a connection.
  • the "ACCEPT" message carries the local keep-alive ( (KA, Keep Active) timer timeout value; if the identity of the local bearer network resource manager is invalid, a message indicating that the corresponding connection cannot be established is returned to the local bearer network resource manager, and the message carries the corresponding reason code
  • the reason code is used to identify the reason why the connection cannot be established.
  • the peer bearer network resource manager When the peer bearer network resource manager sends an "ACCEPT" message, it also needs to start its own peer KA timer and enter the Online state, that is, the peer bearer network resource manager and the local bearer are established locally. QoS connection between network resource managers.
  • the local bearer network resource manager receives the After the "ACCEPT" message, start the local KA timer and enter the Online state, that is, establish a QoS connection between the local bearer network resource manager and the peer bearer network resource manager; if the local bearer network resource manager receives The message sent by the peer bearer network resource manager that the corresponding connection cannot be established, the local bearer network resource manager may re-initiate a connection establishment request to the peer bearer network resource manager as needed.
  • steps 23 and 24 are the control flow for maintaining the established QoS connection.
  • Step 23 When the local KA timer expires, restart the local KA timer, and the local bearer network resource manager adds 1 to the number of local KA timer timeouts to count the number of local KA timer timeouts.
  • a KA message that is, a handshake message, needs to be sent to the peer bearer network resource manager to monitor whether the peer bearer network resource manager is in a normal connection state.
  • Step 24 If the peer bearer network resource manager is in a normal connection state, after receiving the KA message, it will send a KA message to the local bearer network resource manager as a handshake response from the local bearer network resource manager, and restart Start its own peer KA timer and still maintain the Online state of the QoS connection.
  • the local bearer network resource manager receives the KA message sent by the peer bearer network resource manager, clears the number of local KA timer timeouts, and still maintains the online status of the QoS connection.
  • the local bearer network resource manager If the local bearer network resource manager has not received the KA message returned by the peer bearer network resource manager, it will cause the local KA timer timeout to exceed the set allowed value. At this time, the local bearer network resource management The peer will release the established QoS connection. Similarly, if the peer bearer network resource manager has not received the KA message sent by the peer bearer network resource manager, the peer KA timer will time out. At this time, the peer bearer The network resource manager will also release the established QoS connection; adding this QoS connection maintenance mechanism can effectively protect The QoS connection established by the certificate reasonably consumes network resources.
  • the local bearer network resource manager and the peer bearer network resource manager on the bearer network control layer of the communication network can transfer specific quality of service resource control messages to realize the bearer network.
  • the resources of the connected nodes under the resource manager are controlled and managed.
  • the QoS connection can carry various quality of service resource control messages, and the quality of service resource control message carries the communication network. Transmission of service quality information required by a certain service, such as the bandwidth required to perform a certain service, the allowed traffic value, etc., the specific implementation of the method according to the present invention will be further described with reference to FIG. 3:
  • Step 31 Determine the quality of service information required for resource control management between two connected nodes in the bearer network, that is, QoS parameter information, etc., the local bearer network resource manager sends the quality of service resource control to the peer bearer network resource manager.
  • the quality of service resource control message carries the determined quality of service information required by the peer bearer network resource manager to perform resource control management on the corresponding connected node.
  • the local bearer network resource manager also sends the determined service quality information to the connection node managed by itself, and the connection node performs resource control and management operations for the service according to the quality of service information.
  • the resources of the corresponding connection nodes in the bearer network need to be specified according to specific The requirements are controlled and managed to meet the transmission requirements for corresponding services, that is, the resources between the initial connection node and the terminal connection node of the service are controlled and managed.
  • the service shield information in the communication network is usually delivered by the service control layer in the network to the bearer network resource manager of the bearer control layer, and then transmitted between each bearer network resource manager.
  • Step 32 After receiving the quality of service resource control message sent by the resource manager of the local bearer network, the peer bearer network resource manager sends the quality of service control policy determined according to the quality of service resource control message to the connecting node, including the flow mapping installation command And related information.
  • Step 33 After the connected node under the peer bearer network resource manager receives the service quality control policy, it performs corresponding resource control management operations, and sends the peer bearer network resource manager to the service quality control. The response of the strategy.
  • Step 34 After receiving the response to the quality of service control policy and related information sent by the connected node of the subordinate, the peer bearer network resource manager sends a quality of service resource control response to the local bearer network resource manager, thereby ensuring the local bearer The network resource manager accurately knows whether the peer bearer network resource manager reliably receives the corresponding quality of service resource control message, and performs the corresponding resource control management operation at the corresponding connection node.
  • step 34 After the processing steps from step 31 to step 34, the necessary quality of service resource control message transmission between two connection nodes involved in a specific transmission service in the bearer network is realized.
  • the QoS resource request processing flow is as follows :
  • Step 41 When the local bearer network resource manager receives the service shield information to be transmitted from the service control layer, it first needs to initiate a QoS resource request to the peer bearer network resource manager, that is, to the peer bearer network resource management. The router sends a QoS resource request, and then executes step 42.
  • the information carried in the QoS resource request includes:
  • connection identifier ID
  • flow information e.g., flow information
  • QoS parameters e.g., flow information
  • traffic descriptor e.g., traffic priority information
  • data consistency information e.g., data consistency information
  • connection ID If it is a bidirectional QoS resource request passed between CMs, it includes: connection ID, flow Information, QoS parameters, traffic descriptors, label switching path (LSP) connection information, and optionally may further include data consistency information;
  • LSP label switching path
  • connection ID If it is a one-way QoS resource request transmitted between CMs, it includes: connection ID, flow information, QoS parameters, traffic descriptors, LSP connection information, and optionally may further include data consistency information.
  • Step 42 After receiving the QoS resource request sent by the local bearer network resource manager, the peer bearer network resource manager performs service routing and resource allocation, and delivers QoS to the connected node under the peer bearer network resource manager.
  • Resource request that is, sending a flow map installation command to the connected node.
  • the local bearer network resource manager If the local bearer network resource manager and the peer bearer network resource manager also need to pass messages through multiple intermediate bearer network resource managers, the local bearer network resource manager first sends a QoS resource request to the next Hopping intermediate bearer network resource manager, the intermediate bearer network resource manager performs routing and resource allocation, and after the resources are successfully calculated, the hopping intermediate bearer network resource manager or the local bearer network resource manager Return a response to the QoS resource request, and continue to forward the QoS resource request until the peer bearer network resource manager receives the QoS resource request and executes the operation described in step 42.
  • Step 43 After the connection node receives the flow mapping installation command and performs corresponding flow mapping installation processing, it sends a response to the peer bearer network resource manager for the flow mapping installation command.
  • Step 44 After receiving the response to the flow mapping installation command sent by the connecting node, the peer bearer network resource manager sends a response to accept the QoS resource request or reject the QoS resource request to the bearer network resource manager.
  • the information carried in the QoS resource response includes:
  • connection ID the response to the QoS resource request sent by the CM to the CA includes: connection ID, flow information, QoS parameters, and traffic descriptors, and optionally further includes data consistency information
  • response from the CM to the CA to reject the QoS resource request includes: a connection ID, a reason code, and optionally further includes data consistency information
  • connection ID connection ID
  • flow information QoS parameters
  • traffic descriptors LSP connection information
  • connection ID the response to the one-way acceptance of the QoS resource request sent by the CM to the CM includes: connection ID, flow information, QoS parameters, traffic descriptors, LSP connection information, and optionally may further include data consistency information;
  • If the response from the CM to the CM to reject the QoS resource request includes: a connection ID, a reason code, and optionally further includes data consistency information.
  • the specific processing process is shown in FIG. 5 and includes the following steps:
  • Step 51 When a service communication process ends or an abnormal situation causes communication to fail, the local bearer network resource manager needs to send a QoS resource sharpening request to the peer bearer network resource manager to release the QoS allocated for it. At the same time, the resource manager of the local bearer network also needs to issue a flow map delete command to the connection node controlled by its own connection, and the connection node performs a corresponding flow map delete operation according to the received flow map delete command.
  • the information carried in the QoS resource dry release request includes:
  • connection ID a connection ID
  • reason code a reason code
  • data consistency information optionally further includes data consistency information
  • Step 52 The peer bearer network resource manager receives the After the QoS resource release request, the QoS resource release is completed, and at the same time, a command to delete the QoS control policy, that is, a flow mapping delete command, is issued to the connection node controlled by itself, and step 53 is performed.
  • a command to delete the QoS control policy that is, a flow mapping delete command
  • Step 53 After receiving the flow mapping delete command issued by the peer bearer network resource manager and completing the corresponding flow mapping delete operation, the connecting node sends a response to the peer bearer network resource manager to the flow mapping delete command.
  • Step 54 After receiving the response to the stream mapping delete command sent by the subordinate connected node, the peer bearer network resource manager sends a QoS resource response response to the bearer network resource manager.
  • the allocated QoS resources may need to be modified according to the actual needs of the messaging process, such as adjusting the allocated bandwidth Resources, maximum allowed traffic, etc.
  • the specific processing flow for modifying QoS resources is shown in Figure 6, and includes the following steps:
  • Step 61 When the assigned QoS resources need to be modified, the local bearer network resource manager sends a QoS resource modification request to the opposite bearer network resource manager.
  • the QoS resource modification request carries the QoS resource identifier and After modifying the QoS resource information, etc., it is also necessary to send a QoS resource modification message to the connected nodes under its control and management, that is, to issue a flow mapping update command, and the connecting node performs corresponding operations according to the received flow mapping update command.
  • the flow map update operation is implemented to modify the QoS resources.
  • Step 62 After receiving the QoS resource modification request sent by the local bearer network resource manager, the peer bearer network resource manager issues a flow mapping update command to the connected node under its control and management according to the information carried in the QoS resource modification request .
  • the intermediate bearer network resource manager that received the QoS resource modification request will respond accordingly.
  • QoS resource modification requests are forwarded to The next-hop intermediate bearer network resource manager until the peer bearer network resource manager receives the
  • the information carried in the QoS resource modification request includes: a parameter full path maximum transmission unit (PATH MTU), a full label stack depth, a local label stack depth, a traffic description, and the like.
  • PATH MTU parameter full path maximum transmission unit
  • Step 63 After receiving the flow mapping update command issued by the peer bearer network resource manager and performing the corresponding flow mapping update operation, the connecting node sends a response to the peer bearer network resource manager for the flow mapping update command.
  • Step 64 After receiving the response to the flow mapping update command sent by the connecting node from the peer bearer network resource manager, it is learned that the QoS resource modification is successful, and sends a QoS resource modification response to the local bearer network resource manager.
  • the method described in the present invention further includes The process of querying the status of the QoS connection established between the resource manager and the resource manager of the peer bearer network is shown in FIG. 7 and includes the following steps:
  • Step 71 The local bearer network resource manager sends a connection status query request to the peer bearer network resource manager periodically or according to a set condition.
  • the connection status query request carries the connection status information of the local bearer network resource manager.
  • it also sends a connection status query request to the connected nodes under its control, and after the corresponding connection node receives the connection status query request, it returns the QoS connection resource situation to the local bearer network resource manager, and then the local bearer network
  • the resource manager checks the consistency of QoS resources according to the connection resource conditions sent by the connected nodes.
  • Step 72 After receiving the connection status query request sent by the local bearer network resource manager, the peer bearer network resource manager initiates a connection status query to the connected node under its control, that is, sends a connection status query message to the connecting node.
  • Step 73 After the connection status query request sent by the connecting node, a connection status query response is sent to the peer bearer network resource manager, that is, the QoS connection resource status of the connecting node is returned to the peer bearer network resource manager.
  • Step 74 The peer bearer network resource manager performs a QoS resource consistency check based on the QoS connection resource returned by the connecting node, and returns a connection status query response to the local bearer network resource manager, that is, to the local bearer network resource manager. Returns the connection status query report.
  • the intermediate bearer network resource manager also needs to go to the next higher level after receiving the connection status query request. Returns the connection status query report.
  • connection status query report includes:
  • connection status query report sent by the CM to the CA includes: a connection ID, a connection resource status, and optionally further includes data consistency information;
  • connection status query report is sent from the CM to the CM, it includes: a connection ID, a connection resource status, and optionally further includes data consistency information.
  • the intermediate bearer network resource manager when the message transmission between the local bearer network resource manager and the peer bearer network resource manager needs to be implemented through multiple intermediate bearer network resource managers, the intermediate bearer network resource manager only plays a message. The role of the transfer without the need to send the corresponding message to the connected node under its control and management, as the local bearer network resource manager and the peer bearer network resource manager.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Description

在通信网络中提供可靠传输服务质量的方法 技术领域
本发明涉及网络通信技术领域， 尤其涉及一种在通信网络中提供可 靠传输服务质量的方法。 发明背景
随着互联网 （Internet )技术的发展， 网络规模日益增大， 各种各样 的网络服务争相涌现， 先进的多媒体系统层出不穷。 由于多媒体业务等 实时业务对网絡传输时延、 延时抖动等特性较为敏感， 当网络上有突发 性高的文件传输协议 （FTP ) 或者含有图像文件的超文本传输协议 ( HTTP )等业务时， 实时业务的传输性能就会受到很大影响； 另一方 面， 通信网络中的多媒体业务占去了大量带宽， 使得需要网络保证传输 质量的关键业务难以得到可靠的传输。
基于上述需要， 各种为业务传输提供服务质量（QoS )保证的技术 应运而生。 为满足传输 QoS的需求， 互联网工程任务组（IETF ) 已经建 议了一些服务模型和机制。 目前业界比较认可在网络的核心使用区分业 务（Diff-serv )模型便是其中之一。 Diff-serv模型所采用的通过设定优 先等级保障传输 QoS的措施虽然可以提高带宽资源的利用率，但因缺乏 相应的维护管理报文的交互， 对其具体的应用效果难以预测。
为此， 又为骨干网 Diff-Serv模型引入一个独立的承载控制层， 用于 对承载网的资源进行相应的管理。例如，为了推动 Diff-Serv模型的应用， IETF和一些厂商以及研究机构共同推动的服务质量骨干网 （Qbone )试 验网上， 使用承载网资源管理器实现承载网资源和拓朴管理， 即管理拓 朴资源和协调各个 Diff-Serv模型区域的 QoS 能力。 这种资源管理 Diff-Serv方式即为有独立承载控制层的 Diff-Serv模型。
在有独立承载控制层的 Diff-Serv模型中，在承载网资源管理器中配 置了承载网连接节点的资源管理规则和网络拓朴结构， 并由承载网资源 管理器负责为用户的业务带宽请求进行资源的分配。 每个承载网资源管 理器相互之间通过信令传递用户的业务带宽请求和结果， 以及承载网资 源管理器为业务分配的路径信息等。
当承载控制层处理用户的业务带宽请求时 ,将确定用户业务的路径， 并由承载网资源管理器通知边缘路由器、 即承载网的连接节点按照指定 的路径转发业务流。
为满足承载网资源管理器间传输消息的需求， 互联网 2 ( Internet2 ) 专门为各个 Diff-Serv模型管理域定义了相应的带宽代理器（ BB )、 呼叫 代理器（CA )或连接管理器（CM )作为承载网资源管理器； 其中所述 的带宽代理器负责处理来自用户主机、 或业务服务器、 或网络维护人员 的带宽请求， 带宽代理器根据当前网络的资源预留状况和配置策略以及 与用户签订的业务服务等级协定（SLA, Service Level Agreement ), 确 定是否允许用户的带宽请求； 所述的呼叫代理器用于充当业务服务器， 即用于将用户的呼叫接入通信网络； 所述的连接管理器用于使业务层面 能够根据业务需求控制承载网络层面。
但上述基于带宽代理器实现的、有独立承载控制层的 Diff-Serv模型 存在一此问题， 例如， 在带宽代理器间使用的简单跨域带宽代理器信令 ( SIBBS, Simple Inter-domain Bandwidth Broker Signaling )来实现资源 的请求， 该信令仅可用于带宽代理器之间， 而且带宽代理器之间没有资 源同步机制， 即直接通过 SIBBS发送资源请求， 而没有会话的建立和维 护过程， 也没有用于维护管理的报文交互机制。
. 目前， 业界还没有成熟的技术方案来传递用户的业务带宽请求和结 果 , 以及承载网资源管理器为业务请求分配的路径信息等。 发明内容
有鉴于此， 本发明的目的在于提供一种在通信网络中提供可靠传输 服务盾量的方法， 以保证在承载网能够实现对整个网络资源的有效管 理， 保证网络中重要业务传输的可靠性。
为了达到上述目的， 本发明提供了一种在通信网络中提供可靠传输 服务质量的方法， 该方法包含以下步骤： 由上述本发明提供的技术方案可以看出， 本发明在承载网的控制层 上的承载网资源管理器间建立 QoS连接， 并对建立的 QoS连接进行维 护管理， 对于处于在线状态的 QoS连接， 可以承载各种 QoS资源控制 消息并在承载网控制层的各个承载网资源管理器间传送， 从而实现在通 信网络中对业务带宽请求和结果， 以及为业务请求分配的路径信息等信 息的传递。本发明所提供的在承载网资源管理器之间建立 QoS连接的方 法， 实现起来筒单可靠， 且所述的 QoS连接易于维护， 控制性好。
本发明中还实现了承载网资源管理器间的资源同步机制和运行维护 机制，克服了现有技术中使用 SIBBS信令实现资源的请求所存在的带宽 代理器之间未实现资源同步机制的缺点。 另外， 本发明还实现了本端承 载网资源管理器和对端承载网资源管理器之间的资源请求和状态报告 的传递， 进一步完善了所建立的 QoS连接性能。 因此， 本发明的实现使 得承载网的资源可以较为方便地进行统一管理， 为保证网络中重要业务 的传输可靠性提供了技术上的支持。 附图简要说明
图 l a示出了通信网络的组网结构示意图；
图 lb示出了通信网络的承载网资源管理器的组网示意图； 图 2示出了本发明中建立连接的流程图；
图 3示出了本发明中传递服务质量资源控制消息的流程图； 图 4示出了本发明中分配服务质量资源的流程图；
图 5示出了本发明中释放服务质量资源的流程图；
图 6示出了本发明中修改服务质量资源的流程图；
图 7示出了本发明中服务质量连接状态查询的流程图。 实施本发明的方式
下面结合附图对本发明进行详细描述。
本发明中解决了通信网絡中 CM之间或 CA与 CM之间无法通过信 令建立 QoS连接的问题， 以及现有技术中采用 SIBBS来实现资源请求， 在带宽代理器（BB )之间没有资源同步机制的问题。
本发明中所述的在通信网络中提供可靠传输服务盾量的方法的核心 是： 在通信网络中实现各个承载网资源管理器间可靠地传递服务质量资 源控制消息， 各个资源管理器利用服务质量资源控制消息为相应业务提 供需要的服务盾量， 从而保证可以根据业务的传输需求可靠地为其提供 相应的传输服务质量。 本发明中首先需要在承载网资源管理器之间建立 QoS连接， 所述的 QoS连接用于传输月良务质量资源控制消息。 另外， 本 发明还实现在承载网资源管理器之间的资源请求和状态报告， 进一步提 高了在通信网络中提供相应传输服务质量的可靠性。
这样， 本发明中实现了在包括 BB、 CA及 CM之间进行服务质量资 源控制消息的传递， 且传递过程包括建立连接、 维护连接等完整的处理 流程， 可以认为本发明为基于连接初始化协议（RCIP ) 实现的， 基于 RCIP实现本发明的具体处理过程将通过下面的描述进行详细的说明。
现结合附图对本发明的具体实施方式作进一步说明，如图 la、 图 lb 和图 2所示， 本发明中在承载网资源管理器 （CM )之间建立 QoS连接 的过程包括以下步骤：
步驟 21： 确定需要通过位于承载网控制层的承载网资源管理器对承 载网中的资源进行控制管理时， 处于初始状态的本端承载网资源管理器 向处于初始状态的对端承载网资源管理器发送建立连接请求， 例如， 可 以发送 "OPEN" 消息作为建立连接请求， 请求在本端承载网资源管理 器与对端承载网资源管理器间建立 QoS连接。
所述的建立连接请求中承载的信息包括： 发起建立连接清求的承载 网资源管理器标识和认证信息， 以便于对端承载网资源管理器根据所述 认证信息进行是否建立连接的认证。
另外， 所述建立连接请求中还可选地包括数据一致性信息， 所述数 据一致性信息用于保证消息在传送过程中不被篡改， 以及避免非法消息 入侵，数据一致性消息通常包括： 32位（bits )键标识（KEY— ID )、 32bits 顺序号和 96bits摘要组成， 其中， KEY— ID用于标识双方共享的键值和 算法， 顺序号在发送 "OPEN" 消息时进行初始化， 发送后续消息时顺 序增加， 当溢出时从 0重新开始， 以避免非法消息入侵。
所述本端承载网资源管理器通常配置了对承载网资源进行管理所需 的管理规则及承载网的网络拓朴信息， 并可以实现相应的资源控制管理 功能， 如可完成相应带宽请求的资源分配工作， 为网络中的业务请求分 配相应的路径信息等。
在承载网控制层通常包括多个承载网资源管理器，如图 lb中的本端 承载网资源管理器、 多个中间承载网资源管理器和对端承载网资源管理 器， 所述的本端、 中间及对端均为针对某一个具体的 QoS连接而言， 一 个 QoS连接的起始点称为本端承载网资源管理器，终点称为对端承载网 资源管理器， 本端承载网资源管理器与对端承载网资源管理器间传送的 消息所经过的各个承载网资源管理器则称为中间承载网资源管理器。 在 通信网络中， 所述本端承载网资源管理器通常需要经过多个中间承载网 资源管理器最终将相应的消息发送到对端承载网资源管理器， 即通常一 条服务质量资源控制消息需要经过由本端承载网资源管理器出发， 并经 过多个中间承载网资源管理器的过程， 才可以到达对端承载网资源管理 器， 最终由对端承载网资源管理器实现对相应连接节点上的资源控制管 理， 所述连接节点通常为路由器。
步骤 22: 对端承载网资源管理器收到本端承载网资源管理器发送的 "OPEN" 消息后， 对端承载网资源管理器根据收到的认证信息及其身 份标识， 判断发出建立连接请求的本端承载网资源管理器身份的有效 性， 如果本端承载网资源管理器身份有效， 则由对端承载网资源管理器 向本端承载网资源管理器发送建立连接响应， 该建立连接响应中携带有 建立 QoS连接的相关信息， 例如，对端承载网资源管理器可以向本端承 载网资源管理器发送 "ACCEPT" 消息作为建立连接响应， "ACCEPT" 消息中携带有本端保活（KA, Keep Active )定时器的超时时间值； 如果 本端承载网资源管理器的身份无效， 则向本端承载网资源管理器返回无 法建立相应连接的消息， 该消息中携带有相应的原因码， 该原因码用于 标识无法建立连接的原因。
对端承载网资源管理器在发送 "ACCEPT" 消息的同时， 还需要启 动自身的对端 KA定时器， 并进入在线（Online )状态， 即在本地建立 对端承载网资源管理器与本端承载网资源管理器间的 QoS连接。
本端承载网资源管理器收到对端承载网资源管理器发送的 "ACCEPT" 消息后， 启动本端 KA定时器， 并进入 Online状态， 即在 本端承载网资源管理器与对端承载网资源管理器间建立 QoS连接；如果 本端承载网资源管理器收到对端承载网资源管理器发送的无法建立相 应连接的消息， 则本端承载网资源管理器可以根据需要重新向对端承载 网资源管理器发起建立连接请求。
至此， 承载网控制层中的本端承载网资源管理器与对端承载网资源 管理器之间的 QoS连接已经建立，步驟 23和步骤 24则是维持已经建立 的 QoS连接的控制流程。
步驟 23: 当本端 KA定时器超时时， 重新启动本端 KA定时器， 并 且本端承载网资源管理器将本端 KA定时器超时次数加 1 , 以统计本端 KA定时器的超时次数， 同时，还需要向对端承载网资源管理器发出 KA 消息， 即握手消息， 以监测对端承载网资源管理器是否处于正常连接状 态。
步驟 24: 如果对端承载网资源管理器处于正常连接状态， 则收到 KA消息后， 将向本端承载网资源管理器发出 KA消息作为本端承载网 资源管理器发出的握手响应， 并重新启动自身的对端 KA定时器， 且仍 维持 QoS连接的 Online状态。 本端承载网资源管理器收到对端承载网 资源管理器发送的 KA消息， 将本端 KA定时器超时次数清零， 且仍维 持 QoS连接的 Online状态。
如果本端承载网资源管理器一直未收到对端承载网资源管理器返回 的 KA消息， 则将导致本端 KA定时器超时次数超过设定的允许数值， 此时， 本端承载网资源管理器将释放已经建立的 QoS连接； 同样， 对端 承载网资源管理器如果一直未收到本端承载网资源管理器发送的 KA消 息， 则对端 KA定时器将超时， 此时， 对端承载网资源管理器也将释放 已经建立的 QoS连接； 增加了这种 QoS连接维护机制便可以有效地保 证所建立的 QoS连接合理地占用网络资源。
建立了 QoS连接后，在通信网络的承载网控制层上的本端承载网资 源管理器和对端承载网资源管理器间便可以进行具体的服务质量资源 控制消息的传递， 以实现对承载网资源管理器下属的连接节点的资源进 行控制管理。
经过了步骤 21至步驟 24的处理过程后， 建立起了处于 Online状态 的 QoS连接， 该 QoS连接可以承载各种服务质量资源控制消息， 所述 的服务质量资源控制消息中则承载着通信网络中传输某一业务所需的 服务质量信息， 如进行某一业务所需的带宽、 允许的流量值等， 现结合 图 3对本发明所述方法的具体实施方式作进一步说明：
步骤 31 : 确定针对承载网中两个连接节点间进行资源控制管理所需 的服务质量信息， 即 QoS参数信息等， 本端承载网资源管理器向对端承 载网资源管理器发送服务质量资源控制消息， 该服务质量资源控制消息 中承载着确定的、 对端承载网资源管理器对相应连接节点进行资源控制 管理所需的服务质量信息。
同时， 本端承载网资源管理器还将确定的服务质量信息下发给自身 管理的连接节点， 该连接节点根据所述的服务质量信息进行针对该业务 的资源控制管理操作。
在通信网络中， 通常需要对一些重要的业务提供较高级别的传输服 务， 或者需要对某一些业务按照指定的带宽进行传输等， 为此， 需要对 承载网中相应连接节点的资源按照具体的需求进行控制管理， 以满足针 对相应业务的传输需求， 即对所述业务的起始连接节点与终端连接节点 间的资源进行控制管理。
通信网络中的服务盾量信息通常由网络中的业务控制层下发至承载 控制层的承载网资源管理器， 然后在各个承载网资源管理器间进行传 步骤 32:对端承载网资源管理器收到本端承载网资源管理器发送的 服务质量资源控制消息后， 向连接节点发送根据服务质量资源控制消息 确定的服务质量控制策略， 包括流映射安装命令及相关信息等。
步驟 33:对端承载网资源管理器下属的连接节点收到所述服务质量 控制策略后， 进行相应的资源控制管理操作， 并向所述对端承载网资源 管理器发送针对所述服务质量控制策略的响应。
步骤 34:对端承载网资源管理器收到下属的连接节点发送的针对服 务质量控制策略的响应及相关信息后， 向本端承载网资源管理器发送服 务质量资源控制响应， 从而保证本端承载网资源管理器准确地了解对端 承载网资源管理器是否可靠地接收相应的服务质量资源控制消息， 并在 相应的连接节点进行了相应的资源控制管理操作。
经过了步驟 31至步骤 34的处理过程, 实现了在承载网中针对某一 具体传输业务涉及的两个连接节点间进行必要的服务质量资源控制消 息的传递。
为使在本端承载网资源管理器与对端承载网资源管理器间进行服务 质量资源控制消息的传输， 首先需要请求为传输过程分配 QoS资源， 如 图 4所示， QoS资源请求处理流程如下：
步骤 41: 本端承载网资源管理器收到业务控制层下发的待传送的服 务盾量信息时， 首先需要向对端承载网资源管理器发起 QoS资源请求， 即向对端承载网资源管理器发送 QoS资源请求， 然后， 执行步驟 42。
所述 QoS资源请求中承载的信息包括：
如果是 CA向 CM发送的 QoS资源请求， 则包括： 连接标识（ ID )、 流信息、 QoS参数、 流量描述符， 并可选地包括数据一致性信息；
如果是 CM之间传递的双向 QoS资源请求， 则包括： 连接 ID、 流 信息、 QoS参数、 流量描述符、 标签交换路径 ( LSP )连接信息， 并可 选地可进一步包括数据一致性信息；
如果是 CM之间传递的单向 QoS资源请求， 则包括： 连接 ID、 流 信息、 QoS参数、 流量描述符、 LSP连接信息， 并可选地可进一步包括 数据一致性信息。
步骤 42:对端承载网资源管理器收到本端承载网资源管理器发送的 QoS资源请求后， 进行业务路由和资源的分配， 并向对端承载网资源管 理器下属的连接节点下发 QoS资源请求，即向连接节点下发流映射安装 命令。
如果本端承载网资源管理器与对端承载网资源管理器间还需要经过 多个中间承载网资源管理器进行消息的传递， 则本端承载网资源管理器 首先将 QoS资源请求发送给下一跳的中间承载网资源管理器，所述的中 间承载网资源管理器进行路由和资源的分配， 并在资源清求成功后， 向 上一跳中间承载网资源管理器或本端承载网资源管理器返回 QoS 资源 请求的响应， 并继续向前转发所述的 QoS资源请求， 直至对端承载网资 源管理器收到该 QoS资源请求， 并执行如步驟 42所述的操作。
步骤 43: 连接节点收到流映射安装命令， 并进行相应的流映射安装 处理后， 向对端承载网资源管理器发出针对流映射安装命令的响应。
步驟 44:对端承载网资源管理器收到连接节点发送的针对流映射安 装命令的响应后，向本端承载网资源管理器发送接受 QoS资源请求的响 应或者拒绝 QoS资源请求的响应。
所述 QoS资源响应中承载的信息包括：
如果是 CM发送给 CA的接受 QoS资源请求的响应， 则包括： 连接 ID、 流信息、 QoS参数、 流量描述符， 并可选地可进一步包括数据一致 性信息； 如果是 CM发送给 CA的拒绝 QoS资源请求的响应， 则包括： 连接 ID、 原因码， 并可选地可进一步包括数据一致性信息；
如果是 CM发送给 CM的双向接受 QoS资源请求的响应， 则包括： 连接 ID、 流信息、 QoS参数、 流量描述符、 LSP连接信息 , 并可选地 可进一步包括数据一致性信息；
如果是 CM发送给 CM的单向接受 QoS资源请求的响应， 则包括： 连接 ID、 流信息、 QoS参数、 流量描述符、 LSP连接信息， 并可选地可 进一步包括数据一致性信息；
如果是 CM发送给 CM的拒绝 QoS资源请求的响应， 则包括： 连接 ID、 原因码， 并可选地可进一步包括数据一致性信息。
在本端承载网资源管理器与对端承载网资源管理器间承载分配了所 述 QoS资源后， 当消息传递过程结束或通信网络中出现异常情况导致消 息传递无法正常进行而需要结束消息传递过程时，还需要进行 QoS资源 的释放处理， 具体处理过程如图 5所示， 包括如下步骤：
步骤 51: 当一次业务通信过程结束或出现异常情况导致通信无法正 常进行时， 本端承载网资源管理器需要向对端承载网资源管理器发送 QoS资源锋放请求， 以释放为其分配的 QoS资源， 同时本端承载网资源 管理器还需要向自身连接控制的连接节点下发流映射删除命令， 连接节 点根据收到的流映射删除命令进行相应的流映射删除操作。
所述 QoS资源幹放请求中承载的信息包括：
如果是 CA与 CM之间传递的 QoS资源释放请求，则包括：连接 ID、 原因码， 并可选地可进一步包括数据一致性信息；
如果是 CM与 CM之间传递的 QoS资源释放请求，则包括：连接 ID、 原因码， 并可选地可进一步包括数据一致性信息。
步骤 52:对端承载网资源管理器收到本端承载网资源管理器发送的 QoS资源释放请求后， 完成 QoS资源释放， 同时， 还向自身连接控制的 连接节点下发删除 QoS控制策略的命令， 即流映射删除命令， 并执行步 骤 53。
步骤 53: 连接节点收到对端承载网资源管理器下发的流映射删除命 令， 并完成相应的流映射删除操作后， 向对端承载网资源管理器发送针 对流映射删除命令的响应。
步骤 54:对端承载网资源管理器收到下属连接节点发送的针对流映 射删除命令的响应后， 向本端承载网资源管理器发送 QoS 资源幹放响 应。
在本端承载网资源管理器与对端承载网资源管理器间承载分配了所 述的 QoS 资源后， 根据消息传递过程的实际需要还可能需要对分配的 QoS资源进行修改， 如调整分配的带宽资源、 允许的最大流量等， QoS 资源修改的具体处理流程如图 6所示， 包括以下步骤：
步骤 61 : 当需要对已经分配的 QoS资源进行修改时，本端承载网资 源管理器向对端承载网资源管理器发送 QoS资源修改请求， QoS资源修 改请求中携带有需要修改的 QoS资源标识及修改后的 QoS资源信息等， 同时还需要向受其控制管理的连接节点下发 QoS资源修改消息，即下发 流映射更新命令， 所述的连接节点根据收到的流映射更新命令进行相应 的流映射更新操作， 从而实现 QoS资源的修改。
步骤 62:对端承载网资源管理器收到本端承载网资源管理器发送的 QoS资源修改请求后，根据 QoS资源修改请求中承载的信息向受其控制 管理的连接节点下发流映射更新命令。
如果本端承载网资源管理器的 QoS资源修改请求需要经过多个中间 承载网资源管理器才可以到达对端承载网资源管理器，则收到 QoS资源 修改请求的中间承载网资源管理器将相应的 QoS 资源修改奇求转发给 下一跳的中间承载网资源管理器， 直至对端承载网资源管理器收到该
QoS资源修改请求， 并执行步驟 62所述的操作。
所述 QoS资源修改请求中承载的信息包括：参数全程路径最大传输 单元（PATH MTU )、全程标签栈深度、本域起标签栈深度、流量描述等。
步骤 63:连接节点收到对端承载网资源管理器下发的流映射更新命 令， 并进行相应的流映射更新操作后， 向对端承载网资源管理器发送针 对流映射更新命令的响应。
步骤 64:对端承载网资源管理器收到连接节点发送的针对流映射更 新命令的响应后，获知 QoS资源修改成功， 向本端承载网资源管理器发 送 QoS资源修改响应。
为了保证所建立的 QoS连接的两端连接状态的一致性，即保证 QoS 连接两端资源的同步， 从而实现服务质量资源控制消息的可靠传送， 本 发明所述的方法中还包括对本端承载网资源管理器与对端承载网资源 管理器间建立的 QoS连接的状态进行查询的处理过程， 具体的 QoS连 接状态查询处理流程如图 7所示， 包括以下步骤：
步骤 71 : 本端承载网资源管理器定时或根据设定条件， 向对端承载 网资源管理器发送连接状态查询请求， 该连接状态查询请求中携带有本 端承载网资源管理器的连接状态信息， 同时， 还向受其控制管理的连接 节点下发连接状态查询请求， 且相应连接节点收到连接状态查询请求 后， 向本端承载网资源管理器返回 QoS连接资源情况， 然后由本端承载 网资源管理器根据连接节点发送的连接资源情况进行 QoS 资源一致性 的检查。
步骤 72:对端承载网资源管理器收到本端承载网资源管理器发送的 连接状态查询请求后， 向受其控制管理的连接节点发起连接状态查询， 即向连接节点下发连接状态查询消息。 步驟 73: 所述的连接节点发送的连接状态查询请求后， 向对端承载 网资源管理器发送连接状态查询响应， 即向对端承载网资源管理器返回 连接节点的 QoS连接资源情况。
步骤 74:对端承载网资源管理器根据连接节点返回的 QoS连接资源 情况进行 QoS资源一致性检查，并向本端承载网资源管理器返回连接状 态查询响应， 即向本端承载网资源管理器返回连接状态查询报告。
如果对端承载网资源管理器与本端承载网资源管理器间的交互需要 经过多个中间承载网资源管理器， 则中间承载网资源管理器收到连接状 态查询请求后， 也需要向上一级返回连接状态查询报告。
所述连接状态查询 告中承载的信息包括：
如果是 CM发送给 CA的连接状态查询报告， 则包括： 连接 ID、 连 接资源状态， 并可选地可进一步包括数据一致性信息；
如果是 CM发送给 CM的连接状态查询报告， 则包括： 连接 ID、 连 接资源状态， 并可选地可进一步包括数据一致性信息。
本发明中， 本端承载网资源管理器与对端承载网资源管理器间进行 消息的传递需要经过多个中间承载网资源管理器实现时， 所述的中间承 载网资源管理器仅起到消息传递的作用 , 而无需如本端承载网资源管理 器和对端承载网资源管理器那样向受其控制管理的连接节点下发相应 的消息。
总之， 以上所述仅为本发明的较佳实施例而已， 并非用于限定本发 明的保护范围。

Claims

权利要求书
1、 一种在通信网络中提供可靠传输服务质量的方法， 其特征在于， 该方法包含以下步骤：
A、 在通信网络中的承载网资源管理器间建立服务质量连接；
B、 将通信网络在数据传输过程中需要提供的服务质量信息通过所 述服务质量连接在各承载网资源管理器间传播；
C、 与承载网资源管理器相连的连接节点根据承载网资源管理器下 发的服务质量信息， 提供与其相对应的资源。
2、根据权利要求 1所述的方法， 其特征在于， 所述承载网资源管理 器位于通信网络中承载网的控制层。
3、 根据权利要求 1所述的方法， 其特征在于， 所述步骤 A包括初 始建立连接的步骤：
Al、发起建立连接过程的本端承载网资源管理器向对端承载网资源 管理器发送建立连接请求；
A2、 对端承载网资源管理器响应所述建立连接请求， 并建立基于传 输服务质量的连接。
4、 根据权利要求 3所述的方法， 其特征在于， 所述步骤 A2之前进 一步包括： 对端承载网资源管理器判断本端承载网资源管理器的身份是 否有效， 如果有效， 则执行步驟 A2; 否则， 向本端承载网资源管理器 返回无法建立连接的消息。
5、根据权利要求 3所述的方法， 其特征在于， 所述建立连接请求中 承载的信息包括： 发起建立连接请求的承载网资源管理器标识和认证信
6、 根据权利要求 3所述的方法， 其特征在于， 所述步骤 Α2之后进 一步包括：
A3、本端承载网资源管理器定时向对端承载网资源管理器发送握手 消息， 并根据对端承载网资源管理器返回握手响应的情况确定连接的状 态。
7、 根据权利要求 6所述的方法， 其特征在于， 所述步驟 A3包括以 下步骤：
A31、 在本端承载网资源管理器建立本端保活定时器， 在对端承载 网资源管理器建立对端保活定时器；
A32、 本端保活定时器超时时， 本端承载网资源管理器将本端保活 定时器超时次数加 1 , 并向对端承载网资源管理器发送握手消息；
A33、 对端承载网资源管理器收到握手消息后， 重新启动对端保活 定时器， 并向本端承载网资源管理器返回握手响应；
A34、 本端承载网资源管理器根据本端保活定时器的超时次数确定 所建立的服务质量连接状态， 对端承载网资源管理器根据对端保活定时 器是否超时确定服务盾量连接状态。
8、根据权利要求 6所述的方法， 其特征在于， 所述握手消息中承载 的信息包括： 连接标识和连接资源状态信息。
9、 根据权利要求 1或 3所述的方法， 其特征在于， 所述步驟 B为： 本端承载网资源管理器通过一个以上中间承载网资源管理器与对端承 载网资源管理器进行信息交互， 且所述中间承载网资源管理器仅负责消 息的传递。
10、 根据权利要求 1或 3所述的方法， 其特征在于， 所述步骤 B之 后进一步包括： 由最终接收所述服务质量信息的承载网资源管理器， 根 据收到的服务质量信息对受其控制管理的连接节点的资源进行管理控 制。
11、 根据权利要求 1所述的方法， 其特征在于， 所述步骤 B包括以 下步骤：
Bl、 本端承载网资源管理器向受其控制管理的连接节点及对端承载 网资源管理器发送承载有服务质量信息的服务质量资源控制消息；
B2、 对端承载网资源管理器根据接收的服务质量资源控制消息， 向 连接节点发送服务质量资源控制策略；
B3、 连接节点收到所述服务质量资源控制策略后， 向所述对端承载 网资源管理器返回针对服务质量资源控制策略的响应；
B4、对端承载网资源管理器向本端承载网资源管理器返回针对服务 质量资源控制消息的响应。
12、 根据权利要求 11所述的方法， 其特征在于， 步骤 B1中所述服 务质量资源控制消息为： 服务质量资源请求， 且所述服务质量资源请求 中承载的信息包括： 连接标识、 流信息、 服务质量参数和流量描述符。
13、 根据权利要求 11所述的方法， 其特征在于， 步驟 B1中所述服 务质量资源控制消息为： 服务质量资源释放请求， 且所述服务质量资源 释放请求中承载的信息包括： 连接标识和原因码。
14、 根据权利要求 11所述的方法， 其特征在于， 步骤 B1中所述服 务质量资源控制消息为： 服务质量资源修改请求， 且所述服务质量资源 修改请求中承载的信息包括： 连接标识和修改后的、 对应于服务质量资 源连接的参数信息。
15、 根据权利要求 11所述的方法， 其特征在于，
步骤 B1中所述服务质量资源控制消息为连接状态查询消息， 且所述步骤 B4包括：
对端承载网资源管理器收到连接节点发送的所述响应后， 对所建立 的服务质量连接资源的一致性进行检查； 根据检查结果向本端承载网资 源管理器返回针对连接状态查询消息的响应。
16、根据权利要求 15所述的方法， 其特征在于， 所述针对连接状态 查询消息的响应中承载的信息包括： 连接标识， 或流信息， 或服务质量 参数， 或流量描述， 或标签栈， 或路径最大传输单元， 或承载网资源管 理器栈， 或以上任意的组合。
17、 根据权利要求 5、 8、 12、 13、 14或 16所述的传输服务质量的 方法， 其特征在于， 所述的消息中承载的信息进一步包括： 数据一致性 信息。
18、根据权利要求 17所述的方法， 其特征在于， 所述数据一致性信 息包括： 参数全程路径最大传输单元、 全程标签栈深度、 本域起标签栈 深度、 流量描述。
19、根据权利要求 11所述的方法， 其特征在于， 所述连接节点为路 由器。
20、 根据权利要求 1所述的方法， 其特征在于， 所述承载网资源管 理器为带宽代理器， 或呼叫代理器， 或连接管理器。
PCT/CN2004/000870 2003-08-01 2004-07-27 Procede permettant de fournir une qualite de service fiable dans un reseau de communication WO2005013553A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
DE602004027499T DE602004027499D1 (de) 2003-08-01 2004-07-27 Verfahren zur Bereitstellung zuverlässiger Dienstqualität in dem Kommunikationsnetz
AT04738444T ATE470293T1 (de) 2003-08-01 2004-07-27 Verfahren zur bereitstellung zuverlässiger dienstqualität in dem kommunikationsnetz
EP04738444A EP1650895B1 (en) 2003-08-01 2004-07-27 The method of providing reliable quality of service in the communication network
US10/566,739 US7746843B2 (en) 2003-08-01 2004-07-27 Method of providing reliable transmission quality of service in a communication network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN031437702A CN1581791B (zh) 2003-08-01 2003-08-01 在通信网络中提供可靠的传输服务质量的方法
CN03143770.2 2003-08-01

Publications (1)

Publication Number Publication Date
WO2005013553A1 true WO2005013553A1 (fr) 2005-02-10

Family

ID=34109565

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2004/000870 WO2005013553A1 (fr) 2003-08-01 2004-07-27 Procede permettant de fournir une qualite de service fiable dans un reseau de communication

Country Status (7)

Country Link
US (1) US7746843B2 (zh)
EP (1) EP1650895B1 (zh)
CN (1) CN1581791B (zh)
AT (1) ATE470293T1 (zh)
DE (1) DE602004027499D1 (zh)
HK (1) HK1073745A1 (zh)
WO (1) WO2005013553A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8160052B2 (en) * 2005-10-24 2012-04-17 Huawei Technologies Co., Ltd. Method, system and apparatus for synchronizing stream between bearer control layer and bearer layer devices

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100358321C (zh) * 2005-03-08 2007-12-26 华为技术有限公司 下一代网络中实现用户请求模式资源预留的方法
CN100440861C (zh) * 2005-06-13 2008-12-03 中兴通讯股份有限公司 一种ip网络中服务质量的资源申请方法
CN100413254C (zh) * 2005-09-02 2008-08-20 华为技术有限公司 具有独立承载控制层网络中实现资源状态同步的方法
CN100396016C (zh) * 2006-03-01 2008-06-18 华为技术有限公司 在内容分发网络中保障服务水平的系统和方法
CN1983912B (zh) * 2006-04-20 2010-11-10 华为技术有限公司 一种采用滑窗后退方式的数据传输方法
US7764963B2 (en) * 2007-04-11 2010-07-27 Cisco Technology, Inc. GW coupled SIP proxy
WO2009088337A1 (en) * 2008-01-08 2009-07-16 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement in a wireless communication network
CN101635984B (zh) * 2008-07-25 2012-05-16 中兴通讯股份有限公司 一种时分多路传输资源状态同步的方法
US8929878B2 (en) * 2009-05-20 2015-01-06 Qualcomm Incorporated Transaction management
US8582450B1 (en) * 2009-09-30 2013-11-12 Shoretel, Inc. Status reporting system
US8724472B2 (en) * 2010-03-25 2014-05-13 Qualcomm Incorporated Data radio bearer mapping in a telecommunication network with relays
CN102571473B (zh) * 2010-12-29 2015-12-16 中兴通讯股份有限公司 路径故障检测方法及装置
US10218756B2 (en) * 2012-01-06 2019-02-26 Comcast Cable Communications, Llc Streamlined delivery of video content
CN103297461B (zh) * 2012-02-28 2016-05-25 中国移动通信集团公司 Nat会话保活时长设置方法以及客户端和服务器
US9258174B1 (en) * 2013-03-13 2016-02-09 Cisco Technology, Inc. Server-layer path negotiation between client and server network layers
US9201889B1 (en) 2013-03-15 2015-12-01 Emc Corporation Integrated search for shared storage
US9239874B1 (en) * 2013-03-15 2016-01-19 Emc Corporation Integrated search for shared storage using index throttling to maintain quality of service
US9374401B2 (en) * 2013-05-20 2016-06-21 International Business Machines Corporation Communication traffic management
DE102014221956A1 (de) * 2014-10-28 2016-05-12 Bayerische Motoren Werke Aktiengesellschaft Vorrichtung, Fahrzeug, Verfahren und Computerprogramm für einen Relay-Sendeempfänger und eine Netzwerkkomponente
WO2019201747A1 (en) * 2018-04-17 2019-10-24 Telefonaktiebolaget Lm Ericsson (Publ) Dynamic bearer validity

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5461611A (en) * 1994-06-07 1995-10-24 International Business Machines Corporation Quality of service management for source routing multimedia packet networks
WO2000036846A2 (en) * 1998-12-16 2000-06-22 Nokia Networks Oy Method and system for limiting quality of service of data transmission
CN1274221A (zh) * 1999-03-17 2000-11-22 日本电气株式会社 服务质量管理系统和方法
WO2001050790A1 (en) * 1999-12-31 2001-07-12 Nokia Corporation Packet routing in a multi-bearer-type network

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6145006A (en) * 1997-06-25 2000-11-07 Emc Corporation Method and apparatus for coordinating locking operations of heterogeneous host computers accessing a storage subsystem
US7106718B2 (en) * 2001-02-09 2006-09-12 Telefonaktiebolaget Lm Ericsson (Publ) Signaling quality of service class for use in multimedia communicatations
EP1250022A1 (en) * 2001-04-09 2002-10-16 Lucent Technologies Inc. Providing quality of service in a telecommunications system such as a UMTS or other third generation system
EP1250021A1 (en) * 2001-04-09 2002-10-16 Lucent Technologies Inc. Providing quality of service in telecommunications systems such as UMTS or other third generation systems
US20030093526A1 (en) * 2001-11-13 2003-05-15 Koninklijke Philips Electronics N. V. Apparatus and method for providing quality of service signaling for wireless mac layer
CN1283079C (zh) * 2003-02-20 2006-11-01 华为技术有限公司 Ip网络业务质量保证方法及系统
US7193979B2 (en) * 2003-07-11 2007-03-20 Nokia Corporation Method and apparatus for use by a GPRS device in responding to change in SAPI connection
US7801857B2 (en) * 2003-12-19 2010-09-21 Solace Systems, Inc. Implicit routing in content based networks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5461611A (en) * 1994-06-07 1995-10-24 International Business Machines Corporation Quality of service management for source routing multimedia packet networks
WO2000036846A2 (en) * 1998-12-16 2000-06-22 Nokia Networks Oy Method and system for limiting quality of service of data transmission
CN1274221A (zh) * 1999-03-17 2000-11-22 日本电气株式会社 服务质量管理系统和方法
WO2001050790A1 (en) * 1999-12-31 2001-07-12 Nokia Corporation Packet routing in a multi-bearer-type network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CHIMENTO P ET AL.: "Final Report", QBONE SIGNALING DESIGN TEAM, 9 July 2002 (2002-07-09), pages 1 - 44

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8160052B2 (en) * 2005-10-24 2012-04-17 Huawei Technologies Co., Ltd. Method, system and apparatus for synchronizing stream between bearer control layer and bearer layer devices

Also Published As

Publication number Publication date
CN1581791A (zh) 2005-02-16
EP1650895B1 (en) 2010-06-02
US7746843B2 (en) 2010-06-29
DE602004027499D1 (de) 2010-07-15
EP1650895A1 (en) 2006-04-26
US20070053363A1 (en) 2007-03-08
CN1581791B (zh) 2011-06-15
HK1073745A1 (en) 2005-10-14
EP1650895A4 (en) 2007-02-07
ATE470293T1 (de) 2010-06-15

Similar Documents

Publication Publication Date Title
WO2005013553A1 (fr) Procede permettant de fournir une qualite de service fiable dans un reseau de communication
US7561586B2 (en) Method and apparatus for providing network VPN services on demand
JP4607412B2 (ja) 通信ネットワークの方法、サーバ及び構成
EP1777896B1 (en) A method for implementing the customer request mode resource reservation in the next generation network
US20060075042A1 (en) Extensible resource messaging between user applications and network elements in a communication network
WO2008046326A1 (fr) Procédé et système de contrôle de service de réseau
WO2004064325A1 (fr) Systeme et procede de distribution des ressources dans un reseau de communications
WO2006000161A1 (fr) Procede de gestion de reseau
US20070147243A1 (en) Method and system for guaranteeing end-to-end quality of service
WO2010043131A1 (zh) 一种城域网接纳控制的方法及设备与系统
WO2007016848A1 (fr) Procédé de traitement d'une demande de conversion adresse/port de réseau dans un réseau de communication
JP4090999B2 (ja) サービス品質要求の相関
WO2009056013A1 (en) A policy control method and system for layer two device
US7181532B1 (en) Scalable policy server
EP1821455B1 (en) A method for forwarding the traffic flow in the bearer network
WO2009074072A1 (fr) Procédé, système de réseau et équipement de réseau de conversion de stratégie dynamique
EP1758316B1 (en) Method for ensuring reliability in a network including a separate bearer control layer
JP2002158656A (ja) ネットワークアクセス課金システム及び方法
WO2010121531A1 (zh) 一种终端管理系统更新终端状态的方法及终端管理系统
WO2007033612A1 (fr) Systeme et procede de commande de ressource du reseau d'acces
WO2010006492A1 (zh) 一种家庭网关策略控制的装置、系统及其实现方法
JP2012209839A (ja) セッション管理システム、セッション数確保方法およびセッション数確保プログラム
WO2006042464A1 (fr) Procede permettant de gerer les ressources de branchement d'electricite
CN101399755B (zh) 一种dsl设备动态策略控制的方法
KR100766033B1 (ko) 에스아이피와 알에스브이피-티이를 이용한 종단간 서비스품질 보장방법

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 KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL 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): 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 IT LU 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
WWE Wipo information: entry into national phase

Ref document number: 2004738444

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2004738444

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2007053363

Country of ref document: US

Ref document number: 10566739

Country of ref document: US

WWP Wipo information: published in national office

Ref document number: 10566739

Country of ref document: US